From 124211c18bbd4fab67cdf60f4d1a4524864dc0d0 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?G=C3=A9ry=20Debongnie?= Date: Fri, 6 Dec 2019 12:25:55 +0100 Subject: [PATCH] [DOC] clarify store documentation on connected components closes #538 --- doc/reference/store.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/reference/store.md b/doc/reference/store.md index aef98896..5132f9a5 100644 --- a/doc/reference/store.md +++ b/doc/reference/store.md @@ -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 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 -necessary. +`actions`. Owl components can then connect to the store to read their relevant +state, and they will be rerendered if the state is updated. Note: Owl store is inspired by React Redux and VueX.