pb33f/openapi-changes

[Bug] ordering of field should not matter

LasneF opened this issue · 0 comments

here the only difference is the field ordering (eq , neq )

image

    properties:
      field:
        type: string
        description: |
          Label of the parameter to filter on. 
      in:
        $ref: '#/components/schemas/operatorArray'
      nin:
        $ref: '#/components/schemas/operatorArray'
      eq:
        $ref: '#/components/schemas/operator'
      neq:
        $ref: '#/components/schemas/operator'
      le:
        $ref: '#/components/schemas/operator'
      lt:
        $ref: '#/components/schemas/operator'
      ge:
        $ref: '#/components/schemas/operator'
      gt:
        $ref: '#/components/schemas/operator'

vs

   properties:
      field:
        type: string
        description: |
          Label of the parameter to filter on.
      in:
        $ref: '#/components/schemas/operatorArray'
      nin:
        $ref: '#/components/schemas/operatorArray'
      le:
        $ref: '#/components/schemas/operator'
      lt:
        $ref: '#/components/schemas/operator'
      ge:
        $ref: '#/components/schemas/operator'
      gt:
        $ref: '#/components/schemas/operator'
      eq:
        $ref: '#/components/schemas/operator'
      neq:
        $ref: '#/components/schemas/operator'