-
Notifications
You must be signed in to change notification settings - Fork 66
-
Notifications
You must be signed in to change notification settings - Fork 66
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
Updating data property of subroute won't propagate when subroute is not active #75
Comments
It should work if you use a trailing slash? This is indeed confusing and I also encountered with the matching in that sense |
Yeah a trailing slash fixes it. Also the Then through databinding on the root http://localhost:8000/users (note the missing trailing slash) Now if I want to navigate to the detail page (i.e. http://localhost:8000/users/2) through data-binding on the Maybe I am missing something obvious here. |
Yes I encountered this too and I think issue #37 is designated to fix/clear up this behavior. |
As designed, changes to data on inactive routes don't propagate. The thinking here is that this is the less surprising thing, as it would be easy to get into a situation where changing a property that happens to be bound into a distant The subtle distinctions between |
Description
Not sure if by design or a known limitation:
I have a parent route with a
:page
data property and a subroute with an:id
property.If I update the
data
property of a subroute the browser location bar won't propagate, if the subroute is not active/matched.Expected outcome
Original URL: http://localhost:8000/somePage
New URL: http://localhost:8000/somePage/2
Actual outcome
Original URL = New URL = http://localhost:8000/somePage
Reason
This seems to be due to the fact that the subroute is not active and __updatePathOnDataChange will bail out early.
Workaround:
change the
tail.path
of the parentcarbon-route
instead of thedata
property of the subroute.Browsers Affected
The text was updated successfully, but these errors were encountered: