-
-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
continue inlining $$invalidate calls #3548
Conversation
Codecov Report
@@ Coverage Diff @@
## master #3548 +/- ##
=======================================
Coverage 50.25% 50.25%
=======================================
Files 1 1
Lines 197 197
=======================================
Hits 99 99
Misses 98 98 Continue to review full report at Codecov.
|
Found a case where it does not inline it even after these changes. I'll try to find out why this is arising. |
I've tracked down the failing test output to here. I'll try to fix it but it seems like this particular case will be very difficult without large refactoring. |
I think this is ready for review now. I decided not to handle the input event handlers and instead filed an issue with a reproduction: #3553 |
Updated the tests. I'm not sure if you have any strong preferences over this change: - const callback = x`$$value => { $$invalidate('${value}', ${value} = $$value) }`;
+ const callback = x`$$value => $$invalidate('${value}', ${value} = $$value)`; I have it as the latter for personal preference but feel free to change it before merging. |
Thank you — I kept your version without the extra curlies. I think I got in the habit of wrapping arrow functions in curlies back when everything got transpiled to ES5, because it meant adding a |
Continue inlining $$invalidate as a follow-up to #3533
Before submitting the PR, please make sure you do the following
npm run lint
!)Tests
npm test
oryarn test
)