-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Ability to remove states from $stateProvider #1095
Comments
I would very much like to join this request. This feature might not be used very often, but it is very useful for extended use of ui-router. |
I think this has merit but will have to wait until after the current refactor efforts are complete. |
👍 We too are performing lazy state binding. We must make sure that an authenticated (or even a unauthenticated) User can "see" only his states / routes, which is also a security reason! When a user logs out, i am not able to clear the lazy registered routes and this almost seems essential from a security perspective. Unless maybe there is a way to remove or delete a state that I'm not aware of? |
👍 please do this, thx :) |
👍 adding to the chorus! This is def a must have for our post authentication state assignments. |
Yup, noted. It's on the roadmap. Locking the issue before we get bombarded with +1's. |
Closed by 44579ec |
We are perform lazy state binding. This brings the advantage, that a authenticated (or even a unauthenticated) User can "see" only his states / routes, which is also a security reason.
When a user logs out, i am not able to clear the lazy registered routes. I would like this to be implemented. This could be a really interessting feture, because i saw this lazy registration in other SPA's .
Suggested usage:
The text was updated successfully, but these errors were encountered: