You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 16, 2018. It is now read-only.
Right now if you build a template, edit a component, change its values, save those changes, and then hit "back", you're taking back to the "change the values" screen, rather than to the "build the template" screen. It feels like we're doing this:
build template -> history.pushState
tap component edit button
get into edit view -> history.pushState
save change
get back to app view -> history.pushState
tap component edit button
get into edit view -> history.pushState
save change
get back to app view -> history.pushState
when we should probably be doing:
build template -> history.pushState
tap component edit button
get into edit view -> history.pushState
save change
get back to app view -> remove edit state from history
tap component edit button
get into edit view -> history.pushState
save change
get back to app view -> remove edit state from history
That way, in order to "get back" to things like the template menu, you're not first tapping "back" through however many edits you made to your app.
The text was updated successfully, but these errors were encountered:
Right now if you build a template, edit a component, change its values, save those changes, and then hit "back", you're taking back to the "change the values" screen, rather than to the "build the template" screen. It feels like we're doing this:
when we should probably be doing:
That way, in order to "get back" to things like the template menu, you're not first tapping "back" through however many edits you made to your app.
The text was updated successfully, but these errors were encountered: