match segment if remainingPath only consist of unknown qsParams

[jamuhl]

first let me thank you for router5...we right now try to move to router5 from react-router - but encounter one issue that makes it harder then needed for us.

1. we have a lot of querystring params across our app that acts more global then route specific, eg:
   ?lng=...
   ?debug=...

2. we got qs params that act more on some react component, like eg. preselecting some filter

both have in common, that we don't want them to be defined on the route.

sample:
router.addNode('userModify', '/user/modify/:userId')
open http://localhost/user/modifiy/1234?lng=de would result in not found route.

this PR would change it so if a remainingPath in getSegmentsMatchingPath will be ignored if only consist of unmatched querystring params. Personally i think it would make more sense this way. See changed test in commit.

[troch]

Thank you for your PR, I'll review it as quick as I can (might be early next week as I have little time until next week). In the meantime, if you need it urgently, you can use npm's shrinkwrap functionality.

It supports one of my cases too, I am thinking of adding special query parameters which would persist on navigation.

[jamuhl]

No need to rush...and thanks for reviewing.

[troch]

I am merging it but will modify it to make it an option.

[troch]

router5@1.3.0 was released, with support for strictQueryParams option (default to true). Set to false for allowing extra query parameters and still match.

http://router5.github.io/docs/router-options.html#strict-query-parameters

[jamuhl]

great...thanks a lot...