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] store: add some basic documentation

Browse Source
This commit is contained in:
Géry Debongnie
2019-05-10 10:49:14 +02:00
parent 29cc94d567
commit d928927da8
2 changed files with 147 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files
doc/component.md
+3 -3
View File
@@ -351,7 +351,7 @@ We give here an informal description of the way components are created/updated
in an application. Here, ordered lists describe actions that are executed
sequentially, bullet lists describe actions that are executed in parallel.
**Scenario 1: Initial Mounting** Imagine we want to render the following component tree:
**Scenario 1: initial rendering** Imagine we want to render the following component tree:
```
A
@@ -391,7 +391,7 @@ component (with some code like `app.mount(document.body)`).
5. The method `mounted` is called recursively on all widgets in the following
order: `B`, `D`, `E`, `C`, `A`.
**Scenario 2: state change, rerendering**. Now, let's assume that the user clicked on some
**Scenario 2: rerendering a component**. Now, let's assume that the user clicked on some
button in `C`, and this results in a state update, which is supposed to:
- update `D`,
@@ -428,6 +428,6 @@ Here is what Owl will do:
2. `willUnmount` hook on `E`, then destruction of `E`,
3. (initial) patching of `F`, then hook `mounted` is called on `F`
5. patching of `D`,
5. patching of `D`
6. `patched` hooks are called on `D`, `C`