-
Notifications
You must be signed in to change notification settings - Fork 310
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
Bug in binding in a very specific configuration #650
Comments
I managed to find why:
|
If instead of reseting the array, remove one of the item the same bug occurs |
Nice, that's a good explanation. Do you see a solution? |
For this specific case yes, but will be symptomatic. The root issue lays deeper. See http://codepen.io/blikblum/pen/OXBarY Add some items |
I agree, the cause is deep, maybe in the adapter's observce/unobserve functions. |
The issue may be in adapter. See http://codepen.io/jccazeaux/pen/WxaPdm |
I already fixed in my side. Just need a test |
I think i'm close |
😄 |
My working fix is to replace unless callbacks.length
delete map.callbacks[keypath]
@unobserveMutations obj[keypath], obj[@id], keypath with unless callbacks.length
delete map.callbacks[keypath]
@unobserveMutations obj[keypath], obj[@id], keypath It will unobserve mutations only when there are no callbacks left. You have the same? |
The same |
Great, i add it to the PR |
I have a very very specific bug that occurs only when you have
rv-if
with some conditionrv-each
on an array inside therv-if
rv-each
display array lengthFull exemple here
The bug happens when you
rv-if
condition to remove the element (in reality the condition is on the length of the array)rv-if
To get it to work again i must toggle the
rv-if
twice.The text was updated successfully, but these errors were encountered: