Skip to content

noHistory Feature #3417

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
calendee opened this issue Mar 26, 2015 · 1 comment
Closed

noHistory Feature #3417

calendee opened this issue Mar 26, 2015 · 1 comment

Comments

@calendee
Copy link

There are quite a few issues related to overcoming the back view in some apps. Most of the have been closed. I'll try to make a use case as clear as possible.

Scenario 1:

  • App opens
  • User tries to view something
  • They aren't authorized
  • Transition to a Login state
  • User logs in
  • Transition to originally requested state
  • User Happy
  • User goes back
  • User sees login again

Scenario 2;

  • Registered and logged in user opens app
  • Goes to "Contacts" page
  • Realized his BFF is missing from the list
  • Taps "+"
  • Transitions to and Add Contact page
  • Enters the person's name and number
  • Next Button takes to an Addresses page
  • Enters the contacts address info.
  • Saves new contact
  • Goes "back"
  • Is unfortunately seeing the add contact pages again

Scenario # 2 is especially contrived - but it happens. Now, you may be thinking, just do the forms in a modal! Good idea. But in some cases, designers/UX/client doesn't want a modal.

Feature Request:

In the router, be able to add a property like avoidHistory or noHistory. This would indicate that the view in question should never be added to the history stack. This way, after login in, the user will simply go back to the home page.

Right now, people are trying all kinds of ways to prevent the previous view being in their history stack. This feature would solve many of those problems.

FYI : Tried adding this to Trello but doesn't seem possible.

@calendee
Copy link
Author

Reopened as #3418

@ionitron-bot ionitron-bot bot locked and limited conversation to collaborators Sep 6, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants