This repository was archived by the owner on Aug 2, 2022. It is now read-only.
Fixing an issue with response from fetch in the query method#796
Merged
Fixing an issue with response from fetch in the query method#796
Conversation
jeffreyssmith2nd
approved these changes
Sep 11, 2020
|
@bradlhart - Can we merge this PR? |
TaraTritt
approved these changes
Sep 21, 2020
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.
5 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.
Change Description
There is no need to run
.json()on the response as it is already a json result and can be accessed directly. Removing this code to allow query to work as intended.API Changes
Documentation Additions