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
This looks like a bug, since saveForm is indeed declared, and removeThis should have no bearing on it. I'm going to mark it as such.
However, if you're trying to bind a variable through three layers of components like this I'd recommend using a store, since we're probably abusing bindings a bit using the current pattern, and that might cause unexpected results.
Is it really right that just two layers of bind: might (reasonably be expected to) cause unexpected results?
Naively, I think a new user would naturally expect that if nested bind works at all then it should be documented and tested and supported as working - even if it does, say, get slow at high levels of nesting, or blow up on really ridiculously large levels.
Maybe a bug in this REPL: https://svelte.dev/repl/79aa242f7e6d4af684099868189d3cb4?version=3.18.0
If you click on button "toggle modal" in console you should have this warning:
"<Form> was created with unknown prop 'saveForm'"
If you remove from
Form.svelte
export let removeThis = null
{removeThis}
the warning disappear.
Am I wrong?
The text was updated successfully, but these errors were encountered: