ReferenceError: data is not defined

[pateketrueke]

Using let:data from a custom component, and then using data inside a loop along with <select bind:value={anything}> tries to wipe-out data too!

See the example on the REPL: https://svelte.dev/repl/a05cc3a759f341479b56a944d60d4b20?version=3.4.4

Invalidation calls are:

$$invalidate('selected', selected);
$$invalidate('data', data); // `data` is not defined

[Conduitry]

Is this the same as #2942 or is it a separate issue?

[pateketrueke]

I think in my case data should not be touched, bindings are working fine but that additional invalidation makes no sense.

[zinthose]

In reference to #2942 , this may indeed be corollary issues. It appears as though some form of scope is locked into the included components.

[zinthose]

I see now, The issue is with the lack of binding the let: variable.
https://svelte.dev/repl/b4aaaf39a4cf4935a871c33feaa22f99?version=3.4.4

If you bind the let:variable to a locally defined variable there is no error.
In addition, if you don't supply a value to the "selected" variable it properly populates data at initialization. That might also be a bug. atm it's more of a "Gotcha" if the developer assumes the bound value is set from the child component.

[utherpally]

Any new on this?

[JoBurgard]

I came across this in the current version. When this is resolved it would be possible to use components of a library in a more convenient way as you would not have to bind to a variable.