This repository has been archived by the owner on Jul 23, 2024. It is now read-only.
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 was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can be that the API is changed and the open API is not updated?
Are we creating the open API when we build?
Are we updating the auto-generation of the SDK on package?
Sorry, too many questions but maven things are pretty new to me 😅
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Legit questions!
no, because (see next answer :) )
yes!
yes
To recap: at the moment during every
package
phase, the generator first creates theopenapi.json
file from the spring beans, then it generates the SDK source code and the jar.In future PR, I'll move the generation to a following phase (maybe
verify
) to let developer work on their changes without having to deal with all the generated files. Then, the CI will verify if the outcome ofmvn verify
has uncommited changes.