Skip to content

Vuex Tutorial #111

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

Merged
merged 2 commits into from
Mar 24, 2016
Merged

Vuex Tutorial #111

merged 2 commits into from
Mar 24, 2016

Conversation

skyronic
Copy link
Contributor

No description provided.

1. A value may be derived from many other value (think totals, averages, etc.).
2. Many components can use the same getter function.
1. We may want to define getters with computed values (think totals, averages, etc.).
2. Many components in a larger app can use the same getter function.
3. If the value is moved from say `store.count` to `store.counter.value` you'd have to update one getter instead of dozens of components.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we can also mention that getters are efficiently cached for performance (e.g. used by 100 components, but evaluated only once)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh neat! I will do that.

@yyx990803 yyx990803 merged commit 743ad19 into vuejs:master Mar 24, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants