Use latest orval (for API wrapper code generation)#977
Merged
Conversation
Deployed to Cloudflare Pages
|
lukaw3d
force-pushed
the
csillag/use-latest-orval
branch
from
77c3bb8 to
3f7c9f8
Compare
lukaw3d
approved these changes
Oct 30, 2023
csillag
force-pushed
the
csillag/use-latest-orval
branch
from
3f7c9f8 to
b764eb8
Compare
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
There are two version updates of Orval (from 6.17 to 6.18 and then 6.19), and both updates changes the outputted code.
Here, I re-generated our API wrappers with the latest version, using the same input. (Which is not the latest version of the API space; updating to the latest version comes in a separate PR, #948 )