Parameters explicitly define names rather than enumerate them

[earth2marsh]

When defining parameters, they're given as an array rather than as keys. For example:

        - name: latitude
          in: query
          description: Latitude component of location.
          required: true
        - name: longitude
          in: query
          description: Longitude component of location.

versus:

      parameters:
        latitude:
          in: query
          description: Latitude component of location.
          required: true
        longitude:
          in: query
          description: Longitude component of location.
          required: true

This seems in contrast to the patterns set with paths, operations, and responses.

[fehguy]

For parameters, we need the inputs to be consistently ordered. For operations (i.e. paths), they don't need to be except for display purposes.

[earth2marsh]

Ok, then this must be a "won't fix." Since it is a deliberate design choice, it might be a good idea to document the reasoning, no?

[fehguy]

sure thing. I'm going to close this