State to url => order of attributes

[maxiloc]

Following algolia/instantsearch#128

Can we keep the order in the generated url string compared to the trackedParameters

[pixelastic]

Just to clarify, what you would like is that given a trackedParameters of ['query', 'index', 'page'], then you would like the url to look like q=foo&idx=bar&p=0 (with the query string variables in the same order than the trackedParameters array?

This seems feasible for such an easy use-case, but will start to get complicated for the attributes:* that stores all the facets...

Could you expand on your use-case and why you would need this?

cc @bobylito

[maxiloc]

Yes the goal is to be able to have query, index and page before attributes so that it is easy to modify in the url. Right now you can not ensure that.

[bobylito]

What about the parameters that are already in the URL (before we add ours)?

[maxiloc]

For my integrations we can erase them

[maxiloc]

But it could make sense to keep them

[vvo]

Maybe since we are always ordering the parameters (#224) we are could be good here? Because modifying the parameters by hand is something WE developers only do..?

We just need to ensure to always loop using the same order.

Having always the parameters in the same order for everyone may be better here for us to debug/follow?

[maxiloc]

Yes that works but I would just put attributes at the end

[bobylito]

@vvo #224 is not related to that issue.

Predictability is a must :) So the order would be : named parameters, named attributes (we can specify attribute:price) , attribute:*, remaining parameters from the URL that are not ours?

[maxiloc]

@bobylito 👍

[bobylito]

Will PR in qs so that it supports sorting keys. See ljharb/qs#64

[bobylito]

qs 5.2.0 released, let's get back to work! :D

[bobylito]

see #227