fetch should handle Request object usage #91
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
Collaborator
|
Thanks! This looks great! |
github-actions
bot
force-pushed
the
gh-pages
branch
from
8977fc1 to
8ec0324
Compare
github-actions
bot
force-pushed
the
gh-pages
branch
2 times, most recently
from
0d383e5 to
b68decc
Compare
github-actions
bot
force-pushed
the
gh-pages
branch
2 times, most recently
from
6047ce7 to
07a4ac7
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
The Fetch API allows a Request object as the first parameter. Currently, it makes the request when the Request object is used, but the headers are lost. This change populates an existing 'request' variable and tests to ensure the headers are not lost.