If you define a multi query param and leave the value empty (value: ''), when you load the query params you get an array with one element: param: [""] or param:[0] if you are using typeConverter: Number.
This leads to misleading query param data.

Current Behavior

When parsing query parameters based upon the configuration, the matching is done using case sensitive logic.

Desired Behavior

The query parameter parsing should allow for the option to be parsed in a case insensitive manner.
This should be opt-in functionality based upon a conditional flag.

Other Information

This request is created based upon version: 2.3.0

have warning when install on angular 9.1 are they can be ignore?

warning " > [email protected]" has incorrect peer dependency "@angular/common@^8.0.0".
warning " > [email protected]" has incorrect peer dependency "@angular/core@^8.0.0".

When we have a config like:

role: {
          value: '',
          allowedValues: ['Admin', 'Client'],
          multi: false,
          typeConvertor: String,
},
somethingElse: ''

and we open a url like some/resource?role=test&somethingElse=sometext
we should be redirected to some/resource?somethingElse=sometext instead of removeing everything and navigating to some/resource.

Currently the IQueryParamsStoreRoute interface has the queryParamsConfig param set as optional. Not having it on some routes leads to confusing errors.

QueryParamsStoreDefaultMultiValue should able to set minimum, maximum amount of number of item of array, if more than that should auto remove string after separator

When navigating from a route with a set queryParamsConfig and active query params to a route with no config, you get the following error:
TypeError: Cannot read property 'allowedValues' of undefined

When installed with the latest angular the output is:

warning " > [email protected]" has incorrect peer dependency "@angular/common@^7.1.0".
warning " > [email protected]" has incorrect peer dependency "@angular/core@^7.1.0".