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
Using the below code I found that the first team is re-assigned, the second nope (see the console).
Why?
I expect to not get re-assigned when the date is already present.
This may seem negligible, but when there are 30+ components on a page it is not at all (performances).
<script>
importFlatpickrfrom'./flatpickr.svelte';// this assigns team 2 timeslet team = {id:"1", start_date:newDate()};// this not// let team = {id: "1"}; $:console.log("team assigned:", team);
</script>
The text was updated successfully, but these errors were encountered:
I don't think we're doing anything that should cause this, it seems like svelte is doing this on its own somehow. This seems to be a bug in svelte: date properties seem to be reassigned even though they aren't changed at all.
It seems like this is a known bug that might not be fixed until a new major released based on what I gathered from the comments there: sveltejs/svelte#5689
REPL: https://svelte.dev/repl/953050f84c9d4f528ecfaaaf50defbbf?version=3.55.1
Using the below code I found that the first
team
is re-assigned, the second nope (see the console).Why?
I expect to not get re-assigned when the date is already present.
This may seem negligible, but when there are 30+ components on a page it is not at all (performances).
The text was updated successfully, but these errors were encountered: