Auto-save changes in app edit mode

mentioned in issue #32 (closed)

mentioned in issue #101 (closed)

added dev label

mentioned in issue #58 (closed)

We need to figure out how to handle automatic repo updates with auto-save. We either scrape them completely in favor of dedicated publishing (needs more thought) or trigger the repo update only when the user clicks the Done button.

This should also be implemented in way that allows it to be re-used for the translation page.

mentioned in merge request !112 (merged)

mentioned in issue #149 (closed)

mentioned in issue #150 (closed)

I am not sure we can afford to implement a full-blown auto-save in the time we have left and would personally be fine with a warning if the user navigates away with unsaved changes in the form.

I am not sure we can afford to implement a full-blown auto-save in the time we have left and would personally be fine with a warning if the user navigates away with unsaved changes in the form.

+1 for this. I'd also like to polish our current set of features instead of introducing big new ones.

When tackling this, it would probably help to reduce the possibilities for the user to navigate away from the page, such as when removing screenshots and APKs. This could also be done with AJAX requests and JavaScript.

mentioned in issue #157 (closed)

marked this issue as related to #150 (closed)

mentioned in merge request !155 (merged)

mentioned in merge request !157 (merged)

I think the current implementation doesn't lose things anymore when JavaScript is used.

closed