-
Notifications
You must be signed in to change notification settings - Fork 345
"computed" property is called immediately #79
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
Comments
It would seem that the computed property is called immediately, so state is not known yet.
|
@doncatnip , thank you. Seems like this plugin is not 100% compliant with the RFC? |
It certainly isn't. Some shortcomings are documented. This one isn't (if it is indeed one, and not a mistake in the example). It might just be a bug as I would guess computed should only be evaluated on demand. |
Got it. Thank you |
您好,我没理解到为什么使用Object.seal可以解决这个问题呢。 可以指导下嘛 |
I am trying to play with the new composition API.
Installed the plugin and copied the "Basic example" from https://vue-composition-api-rfc.netlify.com/#basic-example.
It throws an exception inside the
computed
getter.The
state
is declared as follows:Am i doing something wrong or is this not supported yet in the plugin?
Thank you.
The text was updated successfully, but these errors were encountered: