refactor: use exhort-api-spec #119
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ruromero
force-pushed
the
external-openapi
branch
2 times, most recently
from
8081c20 to
59923be
Compare
Signed-off-by: Ruben Romero Montes <[email protected]>
ruromero
force-pushed
the
external-openapi
branch
from
59923be to
1b496be
Compare
Strum355
approved these changes
Apr 10, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Remove data model generation from the remote openapi spec and consume directly the exhort-api-spec.
JSON expectations have changed because the library includes the qualifiers and also sorts the fields differently. The contents are the same
Related issue (if any): fixes #118
Checklist