Feature: Add support for REST-API-VERSION based on the used schema #24
Conversation
This file contains 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
…sion header for requests.
yanyongyu
reviewed
Apr 1, 2023
yanyongyu
reviewed
Apr 1, 2023
yanyongyu
approved these changes
Apr 1, 2023
yanyongyu
changed the title
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.
This PR is related to #9 and adds a REST-API-VERSION property for each Rest Client (at first I added it to the RestNamespace but that resulted in circular dependencies, maybe another place is better suited?) and adds an appropriate header when doing requests.
Tested this in my own project using githubkit as there are no tests available.
I did not regenerate the classes itself as this would clutter the PR.