-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
fix(core): do not unnecessarily defer offline transport send #24027
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
Merged
+61
−3
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 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
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
Oops, something went wrong.
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.
m: I think we have a similar issue with
shouldQueue/options.shouldStorebelow. might be worth checking and adjusting while we're at it.Uh oh!
There was an error while loading. Please reload this page.
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.
Good catch, yes, applied that as well.
I wonder if there's a way to make our linter catch this general pattern, where we unconditionally await something that could be a non-promise. 🤔 It could be annoying to be nagged to
isThenable(x)everywhere, but I'm curious now how common this is. It's basically always going to be a correctness and/or performance improvement to avoid theawaitfor sync values.UPDATE: ok, threw a clanker at this question, and I'm now convinced it's not worth doing, so I'm ditching the idea.
thenfunction. However, apart from these two being fixed in this PR, the others are all build-time or startup paths where it doesn't matter as much.isThenable(x) ? await x : xeverywhere would increase bundle size for little gain, and it is uglier to human eyes.send()path, which we'll probably do just by copying the pattern that's fixed here anyway, so there's little added benefit.