Make path-parser replaceable with other library

Hi @troch path-parser has very limited functionality. It would be nice to make it replaceable using some config option.

Also it is not possible to define routes with multiple varying query params.

[mikkelwf]

@troch It would be nice to have options URL params. Especially for routes displaying default / unfiltered content (content without the URL param). Right now the route needs to be registered two times, and the forwardTo does not really change this, since the example with two child routes now totals 3 unique routes.

[aleksandrlat]

Thank you @troch!

Also for url like this http://localhost:3000/user/settings?integrationstab=true&no-rsc-connect param no-rsc-connect does not appear in params of route. I use queryParamsMode = loose And then when I navigate to http://localhost:3000/user/settings?integrationstab=true without no-rsc-connect like this:

route = router5.getState()
delete route.params['no-rsc-connect']
router5.navigate(route.name, route.params)

router5 does not change url to http://localhost:3000/user/settings?integrationstab=true no-rsc-connect still present. Because no-rsc-connect was not parsed correctly. This is one more reason to use another parser.

For using a different parser, I’m unsure about the outcome (whether it’s something which is feasible or not), and I’m not willing to try myself.

Will you accept PR if I implement it?