When compare locations, only path is compared, params are ignored
See original GitHub issueAs you can see in TurboNavRule
private fun locationPathsAreEqual(first: String?, second: String?): Boolean {
if (first == null || second == null) {
return false
}
return URI(first).path == URI(second).path
}
This will cause unexpected pop presentation. Shouldn’t params be compared too? Since params also reflect page state.
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (1 by maintainers)
Top Results From Across the Web
Comparing $location.path() to route with params not working
I have an app where I must allow non logged in users to access some pages, such as forget password form, registration etc....
Read more >Option to match exactPath that ignores query parameters and ...
This request is for the ability to do an exact match but only on the path, not the whole URL, i.e. the exactPath...
Read more >Ignore Order — DeepDiff 6.2.2 documentation - Zepworks
DeepDiff by default compares objects in the order that it iterates through them in iterables. In other words if you have 2 lists,...
Read more >BGP Best Path Selection Algorithm - Cisco
This comparison only occurs if the first (the neighboring) AS is the same in the two paths. Any confederation sub-ASs are ignored.
Read more >gitignore Documentation - Git
When deciding whether to ignore a path, Git normally checks gitignore patterns ... These patterns match relative to the location of the .gitignore...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Thanks @jayohms for putting in the effort to get this fixed and for letting us know, I really appreciate it. 😃
@fffx @jwark I’ve changed the default behavior in #178, but have added a new path property configuration option to restore the previous behavior for any desired paths.