First of all: yes, the issue I will describe is 100% a PEBKAC error.
That being said. Have you ever created an automation, just to accidentally close the tab/browser or like me, have a mouse that has just a little too easy to press button that also takes you back to the previous page?
Yes, I know that when you press the back button on screen there is a dialog prompting to stay or leave, but more often than not I am creating the most elaborate automations only to accidentally close it through closing the browser, tab or clicking back on my mouse and having to start all over again.
That did give me the actual idea, I would also be fine with just a more aggressive dialog when exiting a page with unsaved changes, but this one will be more complicated:
Autosave for automations.
How should they work?
- autosave the automation with every change, not to the actual automation for obvious reasons
- autosaves are stored in an autosaves.yaml file
- clicking the existing save button will “deploy” the automation to the automations.yaml
- opening an automation will either open the latest version, either autosave or saved, or give a promt to continue with the autosaved version or open the saved automation to start editing fresh.
- optional: a “reset” button to reset the automation to the last saved state
To clarify, any usage of saved means manually saved by the user.