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
Describe the bug
TL;DR See the Repl, should be self-explainatory if you change an options and see the console.
I wanted to make a Select component with reactive declarations to filter the options[] provided..
But the reactive declarations with the options[], are called every time the select's bind:value changes, the options are not changing. why it it called more than once?
When you export a variable, it is mutable from the outside, so I can sort-of see why it might receive a state-update twice (once from the parent, and once for itself).
The fact it registers such an update even though the value of the object itself hasn't changed could be improved by doing a deeper comparison, but I'm not 100% sure this would be the case, and I'm not sure what impact this might have on performance.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Describe the bug
TL;DR See the Repl, should be self-explainatory if you change an options and see the console.
I wanted to make a Select component with reactive declarations to filter the options[] provided..
But the reactive declarations with the options[], are called every time the select's bind:value changes, the options are not changing. why it it called more than once?
To Reproduce
REPL
Expected behavior
Reactive stament should only be recalled if any variable it "watches" changes.
Severity
Low, but if i provide a lof of options in the array, it slows the UI to recalculate the same thing
The text was updated successfully, but these errors were encountered: