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
the swagger parser does resolve 3.1 $refs differently than the 3.0 $refs when the resolve option is set. While 3.0 replaces external $refs with internal refs, 3.1 does inline the $ref. That is bad because it looses the "Name" of the $ref which is used/needed to generate (nice) class names.
Resolving $refs manually is too complicated with the swagger parser.
OpenAPI 3.1 will only be possible using the internal OpenAPI parser.
Activity
handle OpenAPI 3.0/3.1 type differences (#251)
hauner commentedon Mar 30, 2025
the swagger parser does resolve 3.1 $refs differently than the 3.0 $refs when the
resolveoption is set. While 3.0 replaces external $refs with internal refs, 3.1 does inline the $ref. That is bad because it looses the "Name" of the $ref which is used/needed to generate (nice) class names.Resolving $refs manually is too complicated with the swagger parser.
OpenAPI 3.1 will only be possible using the internal OpenAPI parser.
hauner commentedon Mar 30, 2025
swagger-api/swagger-parser#2079
handle OpenAPI 3.0/3.1 type differences (#251)
extend test sets (#251)
warn OpenAPI 3.1 (#251)
fix test sets (#251)