-
-
Notifications
You must be signed in to change notification settings - Fork 19
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
Info: Warnings in developer console #11
Comments
Hey, thanks :) Warnings from the svelte compiler aren't issues or problems, necessarily -- it's just how we can notify the developer of potential issues. In this case it's the desired behavior and there's no drawback to it, so I'd rather have simpler component code than potentially convey that you have to do it a more verbose way. Will close, but thanks for double-checking :) |
It's very annoying to have warnings on each navigated page. Can we use stores for params? |
No, not here. In your app you can, or use the workaround mentioned above. Keep in mind this is a demo to jumpstart/illustrate Svelte usage. |
I agree with you, even if i think that production ready applications should not have those warnings. Might indicate the developer has done weird stuff. But as mentioned above, this should just be a notice for other developers also wanting to remove them |
On every page change i got a warning the dev-console that
By using
instead of
in
App.svelte
, and settingparams = undefined
every time your page dost not have any params, you can get rid of this warning.This should just be an info to those who are also annoyed, so feel free to close :D
The text was updated successfully, but these errors were encountered: