ci: fix: use forbid fields during ci #99
Merged
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
Member
tazlin
commented
Dec 26, 2023
•
tazlin
commented
- This changes the default behavior of tests to forbid undefined fields in the objects returned from the API. This change aims to ensure that when SDK versions are published, they account for all of the currently defined objects and fields on the API.
- Incidentally, this PR also brings the SDK model definitions which do exist into compliance with the schema currently on the API, specifically the FindUserResponse model.
tazlin
force-pushed
the
ci-extra-field-forbid
branch
from
332c919
to
245c28c
Compare
tazlin
force-pushed
the
ci-extra-field-forbid
branch
from
245c28c
to
287818c
Compare
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.