"destination": {
i wonder how and if we should address clients request for destination path. in echocast we have the path transform, for example we transform into href/sample/year=2026/month=03/..
4 Matching Annotations
- Last 7 days
-
laughing-bassoon-7p6pm2g.pages.github.io laughing-bassoon-7p6pm2g.pages.github.io
-
-
POST /v4/data/exports/models create → 202 + { jobId }
do we also use client account? as in feed configuration?
-
-
laughing-bassoon-7p6pm2g.pages.github.io laughing-bassoon-7p6pm2g.pages.github.io
-
POST /v4/data/exports/model create → 202 + { jobId }
do we want to support per account requests as we do in feed configuration? to deduce the account from request context?
-
- Jun 2026
-
laughing-bassoon-7p6pm2g.pages.github.io laughing-bassoon-7p6pm2g.pages.github.io
-
The groot field automation (n8n) allows an existing field to be silently overwritten.
wow that's right we shouldn't allow that only send a slack message about the diff https://n8n-wfs-prod.tomorrow.io/workflow/VdmdIGc0PDft89vi
-