-
-
Notifications
You must be signed in to change notification settings - Fork 155
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: create a new NameBuilder scope inside lambda expressions #358
Conversation
Codecov Report
📣 This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more @@ Coverage Diff @@
## main #358 +/- ##
==========================================
+ Coverage 91.71% 92.09% +0.37%
==========================================
Files 109 122 +13
Lines 3379 3870 +491
Branches 438 526 +88
==========================================
+ Hits 3099 3564 +465
- Misses 189 207 +18
- Partials 91 99 +8
... and 1 file with indirect coverage changes 📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
I tried to rebase via github, didn't work out as expected 😢 Could you rebase manually? |
c6862d0
to
8ea2e88
Compare
🎉 This PR is included in version 2.8.0-next.2 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
Update lambda expressions to use a new NameBuilder scope. This should prevent x, x1, x2, x3 appearing in integration tests as much. This change is cosmetic but arguably could make the code harder to read.
Becomes: