Encoding Object examples have invalid schema property

[jeremyfiel]

Reviewing the Encoding Object Examples

The keyword type should be $ref.

         addresses:
            # default Content-Type for arrays is based on the `inner` type (object shown, so `application/json` in this example)
            type: array
            items:
              type: '#/components/schemas/Address'

[jeremyfiel]

I noticed 3.1.0 has a slightly different schema, albeit, valid. Lmk if you want that updated too.

          addresses:
            # default Content-Type for arrays is based on the _inner_ type (object shown, so `application/json` in this example)
            type: array
            items:
              type: object
              $ref: '#/components/schemas/Address'

cc @handrews let me know if this should be fixed too.

[handrews]

@jeremyfiel I'm not sure what would need to be fixed in the 3.1 schema? I might be missing something.

[jeremyfiel]

the `type: object` is redundant with a `$ref` sibling

…

On Wed, Mar 1, 2023 at 2:16 PM Henry Andrews ***@***.***> wrote: @jeremyfiel <https://github.com/jeremyfiel> I'm not sure what would need to be fixed in the 3.1 schema? I might be missing something. — Reply to this email directly, view it on GitHub <#3170 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AHU7MTNBUGCSSRETKM2U533WZ6OA3ANCNFSM6AAAAAAVHIZ7AU> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[handrews]

@jeremyfiel I suspect I put it in there just to emphasize that you can put things next to $ref now :-) I don't much care one way or the other, but I think that's why it's like that.

[jeremyfiel]

i'm impartial.

[handrews]

Let's leave it as-is and just fix it for 3.0.4.

[handrews]

This has been fixed in 3.0.4 and we decided not to change it in 3.1.1.