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 Nov 9, 2021. It is now read-only.
One of the great uses for crumbly is solving the navigation headache of returning to a previous route in heavily nested routes. However, Ember provides resetNamespace to prevent your actual code requiring heavy nesting. I'm not sure if others find this to be an issue, but when resetting the namespace, Crumbly's first route returns to the reset point.
This is problematic because it no longer reflects how our user navigated here. This could possibly be solved by #19, but I also think we could solve it much more easily by not using currentRouteName, and perhaps using currentURL or something similar. I'm not sure if this offers the same route lookup mechanism or not. This might be a breaking change for some users.
Thoughts?
The text was updated successfully, but these errors were encountered:
One of the great uses for crumbly is solving the navigation headache of returning to a previous route in heavily nested routes. However, Ember provides
resetNamespace
to prevent your actual code requiring heavy nesting. I'm not sure if others find this to be an issue, but when resetting the namespace, Crumbly's first route returns to the reset point.This is problematic because it no longer reflects how our user navigated here. This could possibly be solved by #19, but I also think we could solve it much more easily by not using
currentRouteName
, and perhaps using currentURL or something similar. I'm not sure if this offers the same route lookup mechanism or not. This might be a breaking change for some users.Thoughts?
The text was updated successfully, but these errors were encountered: