-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Computed properties break _rerender #6
Comments
cc. @Rich-Harris Maybe Rich can enlighten us... I'm on mobile now, but I'll try to find it later on |
Hmm, I was mistakenly thinking about this sveltejs/svelte#893 Seems like throwing an error is the dev mode behaviour. Where did you get the |
Thank for looking into it. Yup, it's here |
@aphitiel just had a chat with @Rich-Harris and he says what you suggest won't break anything. So feel free to open a PR. Or just let me know if you are busy and I will sort it out. Thanks for the investigative debugging session 😀 |
closed in #7 |
When a component uses computed properties,
_rerender
tries toset()
those, which makes_checkReadOnly
inside the component throw. This leads to a full reload when using svelte-loader with hotReload.I couldn't find way to tell if a property is computed, though a possible workaround seems to be replacing this line with
Although that feels somewhat dirty. What do you think?
The text was updated successfully, but these errors were encountered: