I think its worth considering moving to 3.x specifications for OpenAPI. Ultimately this would best be implemented as a new major version of the module (2.0), or a toggle in the project to allow picking 2.0 vs 3.x. Until we figure out a path forward, this issue will be used to track the issues which would benefit from 3.x support.
The 3.0 spec to allow picking the desired version. I think its important that we determine the major changes before moving forward.
The first major issue where this came up is #2983352: OpenAPI is returning invalid security definitions → , which removes a workaround put in place to implement auth metadata which isn't supported in 2.0.
Active
1.0
OpenApi Docs
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
Hello. I can see that this was opened a while ago so wanted to check its status; is there any progress so far?
OpenAPI schema generation out of the box for JSON:API core feature-set is a deliverable of 🌱 [Meta, Plan] Pitch-Burgh: JSON field storage & JSON field schema support Active . I'm not sure which contrib module that work will eventually go into, but look for movement on that "soon." Let me know if you're interested in helping.