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:
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: