Diego ImbertandClaude Opus 4.8 41b62efd6c fix: unify draft path on content path, drop redundant draft_path ...

Editors used to store a renamed draft's target path in a separate
`draft_path` field (flows/apps/raw-apps) while keeping the deployed path in
the content's own `path`. This was redundant — the original/deployed path is
the URL — and it broke the "path already used" guard: editors passed the
renamed `draft_path` as the Path widget's `initialPath`, so reverting a draft
back to the original path falsely tripped "path already used".

Now every editor binds the Path widget to the content's own `path` (like the
script editor already did), and `initialPath` is always the deployed/original
path. A never-deployed draft seeds the baseline from its own friendly path so
the synthetic `draft_{uuid}` storage key isn't flagged as a rename.

The computed `draft_path` field on list/draft API responses is kept (it's how
the home/Review/Drafts lists render the friendly name) but is now sourced
uniformly from `value->>'path'` for all kinds.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

2026-06-19 09:15:34 +02:00

..

src

fix: unify draft path on content path, drop redundant draft_path

2026-06-19 09:15:34 +02:00

Cargo.toml

feat: cascade trigger script_path on runnable rename + fix trigger permissioned_as (#8823)

2026-04-14 20:42:13 +00:00