OpenAPI 3.0 allows defining possible values for an enum type:
https://swagger.io/docs/specification/v3_0/data-models/enums/
The package currently offers no way to make use of these fields to clarify possible values for something that is effectively an enum type in Go. That means for usability that it forces API users to observe changes in the API or force certain changes to discover the possible values.
I imagine we could define a signature similar to #10 but for enum values instead of object examples.
OpenAPI 3.0 allows defining possible values for an enum type:
https://swagger.io/docs/specification/v3_0/data-models/enums/
The package currently offers no way to make use of these fields to clarify possible values for something that is effectively an enum type in Go. That means for usability that it forces API users to observe changes in the API or force certain changes to discover the possible values.
I imagine we could define a signature similar to #10 but for enum values instead of object examples.