Add content-specific fetch variants.
#1125
Merged
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
dmjio
force-pushed
the
fetch-content-specific
branch
from
fff9bee to
2b4c203
Compare
|
We still need to add support for more content types like |
dmjio
force-pushed
the
fetch-content-specific
branch
from
2b4c203 to
19b580b
Compare
dmjio
force-pushed
the
fetch-content-specific
branch
from
19b580b to
92e0ea0
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.
Instead of a single
fetch, add small utility functions for web requests. Flesh-out on an as-needed basis.In step with #1124 and #1123, this adds utility functions, matching GET, POST, PUT verbs with content types text, json, arrayBuffer and blob data.