FoHoOV
FoHoOV
I believe #11590 is a breaking change that's not clearly mentioned in docs because of how the reactivity system works now.
cannot bind to user-defined bindables (I mean stuff defined with `$bindable`) in each blocks and let our lord svelte fillup the array just like how it does with `bind:this`. related...
> @Azarattum I'd prefer if we just avoided any need for cleanup entirely, so a refactor would be needed. It might make more sense to implement the individual methods one...
This is still in draft mode because in this code: ```svelte import {Set} from "svelte/reactivity"; const data = $state([1,2,3]); const reactiveSet = new Set(data); $effect(() => { console.log("has 1", reactiveSet.has(1));...
@7nik @Azarattum, I completely agree with you. I've marked this as a draft while I try to comeup with a solution (*hopefully*) that addresses this issue. However, as noted in...
fixed some issues thanks to the comments above, also fixes #11515
I came up with better idea to make it more accurate. Because currently it makes signals aware that a change "is going to happen", the correct implementation would be "a...
> I've not had time to look into this deeply yet, will get around to it this week! Also, the lint CI workflow is failing :) Reallyyyy looking forward for...
@trueadm today I actually had time and changed other reactivity package classes to use the this utility as well. marking this as draft again till I complete those
I updated the PR description to include a detailed explanation of what this change does.