Hello.
Today found some ugly bug.
Sample:
router.on({ '/search/:v/:q': { as: 'search', uses: function () { console.log('search', arguments[0]); } }, '/locations': { as: 'home', uses: function () { console.log('root'); } } });
The route search will never work if in its parametrized url will be string '/locations', which is another route path. The callback is never called
In other words, navigation to http://127.0.0.1:8080/#/search/locations/d does not trigger callback, however, http://127.0.0.1:8080/#/search/notlocations/d will work
Hello.
Today found some ugly bug.
Sample:
router.on({ '/search/:v/:q': { as: 'search', uses: function () { console.log('search', arguments[0]); } }, '/locations': { as: 'home', uses: function () { console.log('root'); } } });The route search will never work if in its parametrized url will be string '/locations', which is another route path. The callback is never called
In other words, navigation to
http://127.0.0.1:8080/#/search/locations/ddoes not trigger callback, however,http://127.0.0.1:8080/#/search/notlocations/dwill work