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
This works fine for all the normal URL patterns. However for query based patterns that uses unencoded slashes (/) in their URLs, it seems to choose the first pattern over the second one.
For example
http://www.abc.com/#/abc?page=example/page/1
Although the second pattern should be chosen here, the first pattern is instead chosen and the data shows up as follows:
The text was updated successfully, but these errors were encountered:
arnavmaiti
changed the title
Non URL encoded slashes (/) choosing wrong pattern
Non URL encoded slashes (/) on query params choosing wrong pattern
Nov 24, 2015
arnavmaiti
changed the title
Non URL encoded slashes (/) on query params choosing wrong pattern
Non-encoded slashes (/) on query params choosing wrong pattern
Nov 24, 2015
We have 2 patterns that parses the URLs using crossroads:
This works fine for all the normal URL patterns. However for query based patterns that uses unencoded slashes (/) in their URLs, it seems to choose the first pattern over the second one.
For example
Although the second pattern should be chosen here, the first pattern is instead chosen and the data shows up as follows:
The text was updated successfully, but these errors were encountered: