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
@achrinza Great initiative. It's great to see schemas in OpenAPI 3.1 are aligned with JSON Schema. There is one less mapping to be worried about. I guess switching to OpenAPI 3.1 for LB runtime is fairly easy. The challenge is to wait for other libraries to catch up - such as Swagger UI, Swagger parser, AJV, ...
This issue is to start a discussion on how to go forward with implementing OpenAPI 3.1 once it hits GA.
OpenAPI 3.1.0-rc0 was "recently" released. It brought about new, breaking changes that may affect LoopBack 4's development.
Most notably (but not limited to):
exclusiveMinimum
andexclusiveMaximum
are now numbers)Potential discussion points:
AJV support for JSON Schema Draft 2019-09 is underway:
Full Release Changelog:
Suggestion
Update codebase to utilize OpenAPI 3.1.
Use Cases
Some immediate benefits:
etc.
Examples
N/A
Acceptance criteria
TBD - will be filled by the team.
The text was updated successfully, but these errors were encountered: