Custom querystring parser

[trikadin]

Please, add the opportunity to use custom qs lib instead of built-in.

[posva]

This was shipped in 2.4.0 https://router.vuejs.org/en/api/options.html#parsequery--stringifyquery

[ganigeorgiev]

It is not very clear from the documentation what the parameters and their types are. From the source, I suppose that parseQuery receives a String and stringifyQuery receives an Object.

// https://github.com/ljharb/qs
import qs from 'qs';

const router = new Router({
    routes: [
        // ...
    ],
    // set custom query resolver
    parseQuery(query) {
        return qs.parse(query);
    },
    stringifyQuery(query) {
        var result = qs.stringify(query);

        return result ? ('?' + result) : '';
    }
});

[rayrutjes]

I think we should allow to override the query parsing methods on a per route basis.
When you are trying to use a third party component that has special requirements regarding query parsing, you don't want to change the way existing URLs are parsed.
Does that make sense @posva , is it maybe already possible?

[posva]

@rayrutjes The url being global, I really think that's a bad idea to change it based on the current component. Appart from that I don't think it's even doable

[rayrutjes]

I think you are right @posva, per route doesn't make sense.
Then, I would militate to have a better url parsing by default that handles nested objects & co.
qs works perfectly ;) but we would like to not have existing users to have to change the way urls are parsed for our library.

For now, we are going to make sure that we are compatible with what is supported.

[posva]

I proposed that already some time ago but vue-router is 8.1kb gziped and qs is 2.6gziped.
Most people don't need nesting in queries, so being able to remove 20% of the size for most people is definitely a good thing

[rayrutjes]

Yes I agree, sadly.
We will work on a solution on our side ;)