Files
windmill/frontend
Guilhem LemouelandClaude Opus 5 db44d36d9b fix: report where a script or flow draft deploys to
Review round 2 findings:

- `deployedPath` was resolved in the app branch only, so deploying a script or
  flow by its storage path reported that path as the destination. The preview
  then reloaded the path whose draft the deploy had just removed, and the
  chat's modified-item entry stayed there. The shared deployer deploys at the
  path inside the draft, so read that path after the flush.
- A script draft's chosen name is the value's own `path`, which the draft-to-
  item mapping did not read, so lists and reads showed only the storage path.
- `force` means "deploy over a newer version of this item", which cannot
  answer whether a name clash is the same item. The deploy refuses again, and
  the message names discard_local_draft as the way out of a leftover draft.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
2026-09-23 13:06:52 +02:00
..
…
…
…
…
…
…
…

Windmill frontend

The Windmill frontend written in Svelte 5 + Tailwind CSS

The frontend is under AGPL, see the LICENSE file at the root of this repo