allOf for request bodies does not respect definition order of properties

[cmeeren]

Consider the following definition:

requestBody:
  content:
    application/json:
      schema:
        allOf:
          - properties:
              username:
                description: The user's username (case insensitive)
                type: string
          - oneOf:
              - properties:
                  password:
                    description: The user's password
                    type: string
              - properties:
                  mobile:
                    description: The user's mobile
                    type: string

This results in the following renderings:

I would expect password and mobile to be at the bottom, i.e. in the order they appear in the source code.

Switching the order of the two array items under allOf does not alter the output.

[viralanomaly]

I'm having this problem, too. I have a nightmarism API I'm documenting with multiple nested allOf calls, and it comes out looking awful because of this.

[viralanomaly]

If @RomanGotsiy or somebody else can point me in the right direction, I could try to figure this out. No promises or anything, but it might be worth the effort.

[trip-somers]

I noticed this, too. It seems to be related specifically to allOf. A few selections from my discriminator contain the fields in the expected order, but two very specific ones are in a different order, and for the life of me, I can not figure out why those two get re-ordered.

[trip-somers]

I know this was just closed, but I want to add that my issue was related to a field being defined in two of the allOf schemas. When I corrected this, the field order was predictable and as-defined.

[RomanHotsiy]

Can it be reproduced on the latest redoc@2.0.0-alpha.29?

[trip-somers]

I was just trying to add information for anyone that may write technically invalid OAS 3 specs. I can try to test the double-definition thing later, but I'll probably forget to do it. :-\

Either way, I think my particular issue was Bad Specs rather than a ReDoc bug.

[RomanHotsiy]

Got it! thanks for the update