You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Help us to manage our issues by answering the following:
Describe your issue:
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.
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.
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: