-
Notifications
You must be signed in to change notification settings - Fork 27.2k
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
chore(turbopack): Delete to-resolved-in-loop lint (too low signal) #74113
Merged
Conversation
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 was referenced Dec 19, 2024
Closed
This stack of pull requests is managed by Graphite. Learn more about stacking. |
Stats from current PRDefault BuildGeneral
Client Bundles (main, webpack)
Legacy Client Bundles (polyfills)
Client Pages
Client Build Manifests
Rendered Page Sizes
Edge SSR bundle Size
Middleware size
Next Runtimes
build cache
Diff detailsDiff for main-HASH.jsDiff too large to display |
Tests Passed |
kdy1
approved these changes
Dec 19, 2024
sokra
approved these changes
Dec 19, 2024
bgw
force-pushed
the
bgw/improve-to-resolved-in-loop
branch
from
December 20, 2024 01:50
d9c8c34
to
89838c8
Compare
bgw
force-pushed
the
bgw/rm-to-resolved-in-loop-lint
branch
from
December 20, 2024 01:50
cd88f0f
to
1495219
Compare
bgw
force-pushed
the
bgw/improve-to-resolved-in-loop
branch
2 times, most recently
from
December 20, 2024 02:06
8648a59
to
89c39b2
Compare
bgw
force-pushed
the
bgw/rm-to-resolved-in-loop-lint
branch
from
December 20, 2024 02:06
1495219
to
7fd7067
Compare
bgw
changed the base branch from
bgw/improve-to-resolved-in-loop
to
graphite-base/74113
December 20, 2024 03:20
bgw
force-pushed
the
graphite-base/74113
branch
from
December 20, 2024 03:21
89c39b2
to
bc69d97
Compare
bgw
force-pushed
the
bgw/rm-to-resolved-in-loop-lint
branch
from
December 20, 2024 03:21
7fd7067
to
7e978f9
Compare
bgw
force-pushed
the
bgw/rm-to-resolved-in-loop-lint
branch
from
December 20, 2024 03:21
7e978f9
to
d4277f7
Compare
Merge activity
|
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.
Had a discussion with @sokra about this during office hours. We were in agreement to delete this, not because it's usually wrong, but just because it's not high-signal enough:
to_resolved().await
are on simple constructor calls, so it doesn't really matter if they're sequential. We could add some heuristics for this, but they'd be imperfect.to_resolved().await
isn't actually what drives the work forward, it's the function call that schedules the work, so in some cases this isn't accurate (and you can't know without type information).Closes PACK-3678