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
fix: use a new includedLabels in the body of the LabeledStatement #5297
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Thank you for your contribution! ❤️You can try out this pull request locally by installing Rollup via npm install rollup/rollup#xiaopi-fix-5292 Notice: Ensure you have installed Rust nightly. If you haven't installed it yet, please first see https://www.rust-lang.org/tools/install to learn how to download Rustup and install Rust, then see https://rust-lang.github.io/rustup/concepts/channels.html to learn how to install Rust nightly. or load it into the REPL: |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #5297 +/- ##
=======================================
Coverage 98.82% 98.82%
=======================================
Files 232 232
Lines 8968 8974 +6
Branches 2338 2338
=======================================
+ Hits 8863 8869 +6
Misses 46 46
Partials 59 59 ☔ View full report in Codecov by Sentry. |
d55788a
to
1c97b0a
Compare
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.
I think the solution makes sense. There is one thing that worries me, though, but I could not produce an error from this: Usually, the label logic should be symmetric between hasEffect
and include
, which is no longer the case here.
The other thing is that I do not understand why I need a switch statement to create the error and cannot just create it with nested block scopes and functions.
Yeah, I also feel a bit worried about this 😨. |
0c6efc1
to
a0c0ad0
Compare
This PR has been released as part of rollup@4.9.1. You can test it via |
This PR contains:
Are tests included?
Breaking Changes?
List any relevant issue numbers:
resolves #5292
Description