NextERP/owl
2
0
Fork 0
mirror of https://github.com/odoo/owl.git synced 2025-10-06 19:59:41 +07:00
Code Issues Packages Projects Releases Wiki Activity

[DOC] clarify store documentation on connected components

Browse Source 
closes #538
This commit is contained in:
Géry Debongnie
2019-12-06 12:25:55 +01:00
parent be8c3bbf6f
commit 124211c18b
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
doc/reference/store.md
+2 -2
View File
@@ -25,8 +25,8 @@ component should own which part of the state.
Owl's solution to this issue is a centralized store. It is a class that owns Owl's solution to this issue is a centralized store. It is a class that owns
some (or all) state, and lets the developer update it in a structured way, with some (or all) state, and lets the developer update it in a structured way, with
`actions`. Owl components can then connect to the store, and will be updated if `actions`. Owl components can then connect to the store to read their relevant
necessary. state, and they will be rerendered if the state is updated.
Note: Owl store is inspired by React Redux and VueX. Note: Owl store is inspired by React Redux and VueX.