Repository navigation
Refresh the schema and regenerate the client - #4
Merged
Merged
Conversation
Generated from https://wger.de by the regenerate workflow.
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
1 participant
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.
Generated from
https://wger.de.Review the diff of
schema/wger-openapi.yamlfor removed endpoints, changedresponse types, new required parameters and renamed
operationIdvalues.A rename will also change the s name in the generated client, which breaks its
consumers even when the API itself did not change.
After merging:
uv version x.y.zgit tag x.y.z && git push origin x.y.zgh release create x.y.z --generate-notes