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 has resurfaced, or never went away. I can't figure out what I do to trigger it, but it's not hard. It may have something to do with putting something that causes a compilation error into a child component, even temporarily.
The REPL app gets into a weird state where changes to one component affect multiple components, and the options in the dropdown menu do not always match the current names of the files.
The text was updated successfully, but these errors were encountered:
It might be triggered by the compiler throwing an exception that the REPL doesn't know how to deal with (e.g., because of a bug in the compiler, rather than an issue we found in the user's component). If I go to https://svelte.technology/repl?version=1.18.0&example=nested-components and type in something that makes the compiler crash (e.g. {{yield}} next to another element, bug), the REPL gets into a bad state and seems to stay that way until I refresh the page.
Conduitry
changed the title
REPL: Weird bindings with multiple components
Unknown compiler exceptions mess up REPL state
Apr 25, 2017
This has resurfaced, or never went away. I can't figure out what I do to trigger it, but it's not hard. It may have something to do with putting something that causes a compilation error into a child component, even temporarily.
The REPL app gets into a weird state where changes to one component affect multiple components, and the options in the dropdown menu do not always match the current names of the files.
The text was updated successfully, but these errors were encountered: