Support x-fern-availability OpenAPI extension on the property-level

[bdbyrne]

The x-fern-availability extension is currently supported on endpoints, however it'd be useful to support this at the propery level, namely to document which fields are beta vs. generally available.

I could imagine it'd have to look like the following to handle $refs:

some_object:
  type: object
  properties:
    field1: ...
    field2: ...
  x-fern-availability:
    field1: beta
    field2: generally-available

We also scope the beta tag down to enum values, if that's also an option. But field-level would be good enough for our use case.

[dannysheridan]

Thanks for filing. Right now, you can control availability at the endpoint level. It makes sense for us to extend this control to the property level. This aligns with our roadmap as it gives you more control over how your API docs render to developers. Will keep you updated here.

[RohinBhargava]

Hi @bdbyrne!

We are currently in the process of writing an OpenApi Parser that will handle conversion in a first-class way. I have noted this as something to include in our property parsing. Please let us know if there are other features that we can support. As Danny mentioned, we'll keep you updated with this here.