[TT-8528] Improper handling of non-nullable fields in OpenAPI #350
Conversation
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
|
Kudos, SonarCloud Quality Gate passed!
|
pvormste
approved these changes
May 10, 2023
rhianeKobar
approved these changes
May 10, 2023
kofoworola
approved these changes
May 10, 2023
buraksezer
deleted the
feat/TT-8528/Improper-handling-of-non-nullable-fields-in-OpenAPI
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 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.
PR for TT-8528
Now, we can handle non-nullable fields properly. There was also a minor bug in a function that generates mutation type. It was swallowing the parameters if a request body defined for the same operation id. This bug has also been fixed.