Files remain "unsaved" after Run about zapp.run

[Ehesp]

Yeah this is currently the expected behaviour, however I'm not sure whether it is the correct behaviour.

Part of the issue we saw with running triggering a save, is say you're working on updating an existing project you want to build the results to check things are working as intended (they might not be). If its a popular project, you'd potentially be saving broken builds each time you run.

Happy to discuss this one as we want to make sure that the experience feels correct

[Salakar]

This has been reworked entirely in the latest version which is now live, please try it out, thanks

[slovnicki]

Ah, I see.

Then it may be a good thing to have a "Save on Run" toggle that can be false by default.

We'll see what others think about this...