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
it will be the object property used on query string
Click on Update route button
it will replace the route, using the object on query string
the query string will be rendered in the <code> tag
Change the value on the input and click on Update route again
What is expected?
The query string is updated with the new value on the object property.
What is actually happening?
The query string remains the same, ignoring the change on object's property.
After some digging in the code, I think I found the object comparison method used in confirmTransition method (which uses isSameRoute), and it does a simple "non-deep" comparison of properties on query string. Since it's using an Object on the query string, it should do a deep (recursive) comparison of Object properties.
The text was updated successfully, but these errors were encountered:
ppdeassis
changed the title
Object in query string parameters do not trigger "route change" if its properties changes
Object in query string parameters does not trigger "route change" if its properties changes
Jun 15, 2017
Version
2.5.3
Reproduction link
http://jsfiddle.net/6znsr5wd/3/
Steps to reproduce
Access Home
input
Update route
buttonreplace
the route, using the object on query string<code>
taginput
and click onUpdate route
againWhat is expected?
The query string is updated with the new value on the object property.
What is actually happening?
The query string remains the same, ignoring the change on object's property.
After some digging in the code, I think I found the object comparison method used in
confirmTransition
method (which usesisSameRoute
), and it does a simple "non-deep" comparison of properties on query string. Since it's using an Object on the query string, it should do a deep (recursive) comparison of Object properties.The text was updated successfully, but these errors were encountered: