-
-
Notifications
You must be signed in to change notification settings - Fork 98
fix: Skip DOM Nodes loaded in the same mutations run #744
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: Skip DOM Nodes loaded in the same mutations run #744
Conversation
4fb4adb to
38948f2
Compare
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #744 +/- ##
=======================================
Coverage 73.76% 73.76%
=======================================
Files 198 198
Lines 20352 20362 +10
=======================================
+ Hits 15012 15021 +9
- Misses 5340 5341 +1 ☔ View full report in Codecov by Sentry. |
| // this is mainly due to nodes being created in the same run as when this function (remove) is being called, | ||
| // like nodes created by loaded templates. | ||
| // In this case we can safely skip these nodes. | ||
| if !does_node_have_state { |
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.
Nitpicking: Maybe just call the variable node_state_is_empty = layer_state.is_none() so we don't have to think about the ! 😄 .
|
Looks nice. I'll give it a quick test when I'm free. |
|
Works great for me! |
ZeroX-DG
left a comment
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.
LGTM 🎉
Closes #602