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
Many objects contain description, title/summary, deprecated, externalDocs, example. It would make the spec a lot more readable if these were filtered out through traits or inheritance.
The text was updated successfully, but these errors were encountered:
I am creating a Java API for swagger and found that there seems a lot of similar concepts specified multiple times. I like to factor that out of course with inheritance and traits.
This has largely been done in the 3.1 schema, as JSON Schema draft 2020-12 has more flexible re-use constructs.
Also, in 3.1, summary and description can be overridden in the Reference Object.
Given the age of this and how much things have changed since 2.0, I'm going to close this, but do feel free to open a new issue based on the current state of the spec if you think there is work of this sort to be done now. Or join the discussions for 4.0 in the OAI/sig-moonwalk repository, where we can make more substantial changes to the format.
Many objects contain description, title/summary, deprecated, externalDocs, example. It would make the spec a lot more readable if these were filtered out through traits or inheritance.
The text was updated successfully, but these errors were encountered: