Allow required as sibling of $ref (like summary/description)

[radicarl]

Hello,

it would be great for reusability if I could overwrite the required field of parameter and header objects, like I can overwritesummary and description in OpenAPI 3.1.

paths:
  /my-resource:
    parameters:
      - $ref: '#/components/parameters/Accept'
        required: true
    get:
      # some definition

components:
  parameters:
    Accept:
      name: Accept
      in: header
      required: false
      schema:
        type: string

[MikeRalphson]

Thanks for this. We deliberately started small with the scope of this feature with the hope of collecting more data points about what properties people would find it useful to override. In this example we would currently have to say you could not override required: true of an in: path parameter with a false value, but otherwise, I can see how this would be useful.

[PixnBits]

maybe similar to #2089, PR to v3.1 in #2181

[JameelKhan9]

similar to #2026

[handrews]

Folks interested in this topic will likely be interested in the general referencing discussion that has recently started. Keywords adjacent to $ref outside of JSON Schema make for a very tricky topic.

[handrews]

If we implement #1502 in 3.2, we won't need to do anything for this because when using the Encoding Object approach to form-urlencoded, all fields are one schema, and JSON Schema 2020-12 already allows putting any keyword next to $ref (which acts like an allOf, not a merge or overwrite).