-
Notifications
You must be signed in to change notification settings - Fork 2.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Reevaluate window.fetch
each time HttpLink
uses it, if not configured using options.fetch
#8603
Merged
Merged
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Question: There should no runtime difference between
maybe(() => fetch)
andbackupFetch
, asbackupFetch
is alsomaybe(() => fetch)
. In both cases thefetch
variable is resolved during execution time of the maybe lambda. What is reason for thebackupFetch
fallback / the extramaybe(() => fetch)
?What is the reason for
backupFetch
here?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@bripkens A
maybe(() => fetch)
expression executes the() => fetch
function immediately and returns the current result, orundefined
if the function threw an exception. It's the shortest way I've found to evaluate possibly-undefined global variables without obtaining a reference to the global object, and TypeScript infers the return type reliably.To my way of thinking, this means the
maybe(() => fetch)
expression we evaluate here could be different frombackupFetch
, which was evaluated when the module was first imported (possibly long ago). I think this difference allowswindow.fetch
to be wrapped after theHttpLink
is created (the goal of #7832, IIUC). If we switch topreferredFetch || backupFetch
here, then we're stuck with one of those values for all time.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh, my bad, sorry @benjamn. I misunderstood what
maybe
is doing! :)There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A
typeof fetch === "undefined"
check might be clearer, but that’s a nit. I don’t like thismaybe()
function or relying on thrownReferenceError
in a callback, but I can tolerate it.