-
Notifications
You must be signed in to change notification settings - Fork 51k
[Flight] Make debug info and console log resolve in predictable order #33665
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
+375
−120
Merged
Changes from 1 commit
Commits
Show all changes
10 commits
Select commit
Hold shift + click to select a range
402aedb
Ensure blocked debug info entries resolves in order
sebmarkbage 033685b
Revert types
sebmarkbage 378a323
Ensure blocked console log entries resolves in order
sebmarkbage b7e20be
Block on debug info to resolve before resolving a chunk
sebmarkbage c19cfe7
Add test
sebmarkbage 9253c37
Lazily initialize debug chunks in a linked list
sebmarkbage 915877a
Eagerly initialize debug chunks since the current consumers assume it
sebmarkbage 28aaa3d
Forwarded debug info needs to come before the row completes or it won…
sebmarkbage 9ec0211
Don't block chunks on debug channel if it's not wired up
sebmarkbage a65bb22
Don't add null placeholder
sebmarkbage 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
Ensure blocked console log entries resolves in order
- Loading branch information
commit 378a3234e4fe00f05ab0a982519711d3afb7d71d
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
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.
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.
Where does this error? I'm not seeing any lint errors.
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.
In your version it does not error. I wanted to suggest adding the tuple labels. And then it would error unless we disable eslint. Devon did the same here:
react/packages/react-server-dom-parcel/src/shared/ReactFlightImportMetadata.js
Lines 12 to 20 in 3cfcdfb
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.
Given how much trouble we've had with parsers I'm not sure I trust that this won't break linting elsewhere.