Add routes in order of depth in 'on' method #39
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This change means routes with deeper urls will be given priority.
From the README:
This will no longer be the case. If the 'products' route is added before 'products/:id', resolving to 'products/42' will match the 'products/:id' route. When using
on
routes will then be added in the order of depth (number of segments in the route).This also prevents a possible issue from looping through the 'routes' object in the 'on' method- because ECMAScript specification does not guarantee that the keys of Objects will be in order given a for-let loop.