This repository was archived by the owner on Apr 11, 2024. It is now read-only.
Merged
Conversation
paulomarg
force-pushed
the
allow_typing_request_responses
branch
from
2d11be0 to
14512a1
Compare
paulomarg
commented
Aug 5, 2022
JaKXz
reviewed
Aug 5, 2022
JaKXz
reviewed
Aug 5, 2022
teddyhwang
approved these changes
Aug 5, 2022
JaKXz
reviewed
Aug 5, 2022
6 tasks
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 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.
WHY are these changes introduced?
Currently, when getting data from either the GraphQL or REST clients, the caller needs to manually cast the returned type which makes it more difficult than it needs to be to type the responses properly.
WHAT is this pull request doing?
Adding the option of typing the bodies of request responses when calling the appropriate methods.
Type of change
Checklist