You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While this library sticks to the literal spec type definition, we have noticed many real world specs which do accept refs in this field. Since even the upstream spec is not well defined here perhaps this library should be more lax?
I have noticed that while the upstream openapi 3 spec for discriminator object specifies the data type is
Map[string]string
, in their written examples they use refs: https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.0.3.md#discriminator-objectWhile this library sticks to the literal spec type definition, we have noticed many real world specs which do accept refs in this field. Since even the upstream spec is not well defined here perhaps this library should be more lax?
Curious to hear opinions about this. I have also raised an issue upstream about this: OAI/OpenAPI-Specification#4138
The text was updated successfully, but these errors were encountered: