The order of query parameters should be preserved

[ddossot]

The query parameters are getting alphabetically re-ordered, which can be damaging.

Consider the case when the RAML spec defines the following query params:

from:
to:
offset:
limit:

There is a logic in their ordering: for an end user, seeing from next to to is helpful information. Having to scroll down to find out that both params exist after being alpha re-ordered is counter-productive.

[usarid]

+1 -- agree completely, we need to fix our parsers to preserve such order
of sibling properties, and we need to make sure RAML 1.0 formalizes that
need.

On Fri, Jan 30, 2015 at 10:34 AM, David Dossot notifications@github.com
wrote:

The query parameters are getting alphabetically re-ordered, which can be
damaging.

Consider the case when the RAML spec defines the following query params:

from:
to:
offset:
limit:

There is a logic in their ordering: for an end user, seeing from next to
to is helpful information. Having to scroll down to find out that both
params exist after being alpha re-ordered is counter-productive.

—
Reply to this email directly or view it on GitHub
#99.

[mgogov]

+1

[shravanak]

+1

[janadeau]

+1

[tonyleigh]

+1

[blakeembrey]

Hi everyone! The patch for this was released in the JS RAML parser last week with 0.8.11 (raml-org/raml-js-parser#141). Once we update the parser version, all resources should start resolving in the correct order. /cc @jcenturion

[sichvoge]

The current parser seems to preserve ordering (see image output working with the parser) but the console is doing something that basically bring them back into alphabetical order.

[lukasgeiter]

The problem is that query parameters, type properties and similar lists are all stored as JavaScript objects which have no particular order. To preserve ordering, this data would have to be stored using arrays.

[Skorpyon]

Any updates?
Api-console sort alfabetical ALL prorerties in DataTypes, queryParameters and everywhere
Is is ugly.

[sichvoge]

the original OP was actually fixed, but it seems that the type properties are in alphabetic order now. We will work on that.