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
Inconsistent state handling inside loops #3007
Labels
Comments
Thank you for reporting this issue. This edge case can be only fixed by a major release, I think I could use a proxy instead of cloning the loop context from the parent scope. I am not sure if switching to a proxy is really a breaking change but I can imagine that some other Riot.js users might have other bugs by introducing this change in a minor release. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Help us to manage our issues by answering the following:
I noticed sometimes that when I update the component inside a callback inline in the html element it updates correctly but the state object remain unchanged.
Trying to understand what was going on I noticed that this happen when the inline-callback is inside a loop.
See the console.log in the example below.
example repro
Firefox Windows
Latest
The text was updated successfully, but these errors were encountered: