Properly model querystring input which can contain multiple values

[xealot]

I'm submitting a ...

• bug report
• feature request

Current behavior

In the old router, the new router and the very new router querystring parameters always are accessible as {[k:string]:string}. To pass an array of values via the querystring we have to rely on encoding within the application to serialize and then deserialize the array. We should be able to simply rely on existing URL standard behavior.

Adding to my frustration, there is already a class, URLSearchParams that fully models the querystring but seems unused when retrieving url search params from the router.
https://angular.io/docs/ts/latest/api/http/URLSearchParams-class.html

Expected/desired behavior

When retrieving data parsed from a querystring it should be presented either in a datastructure that supports the standard or in a class that models it properly.

const q: Observable<URLSearchParams> = r.routerState.queryParams;

const q: Observable<{[k:string]:string[]}> = r.routerState.queryParams;

My vote is for the URLSearchParams version of course.

[xealot]

Cross posted to https://github.com/angular/vladivostok/issues/35

[pkozlowski-opensource]

There is no point of duplicating it here if it was reported in angular/vladivostok#35 where the new router lives.

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}