mirror of
https://github.com/odoo/owl.git
synced 2025-10-06 19:59:41 +07:00
Aaron Bohy
af4f372506
Re-render the component all the time before remounting it, which seems safer anyway. In the test, we had to add a nextTick to wait for the changes to be notified (before, we waited thanks to the additional call to mount). If we don't do the nextTick, mount is called, and render is called right after (before the promise returned by mount is resolved). This scenario doesn't work right now (see #441). Closes #381
🦉 OWL Documentation 🦉
Reference
- Animations
- Component
- Configuration
- Context
- Environment
- Event Bus
- Hooks
- Misc
- Observer
- QWeb
- Router
- Store
- Tags
- Utils
Learning Resources
- Quick Start: create an (almost) empty Owl application
- Tutorial: create a TodoList application
- Environment: what it is and what it should contain
Miscellaneous
Architecture
This section explains in more detail the inner workings of Owl. It is targeted for developers working on Owl itself.
Owl Content
Here is a complete visual representation of everything exported by the owl
global object (so, for example, Component is available at owl.Component,
and EventBus is exported as owl.core.EventBus):
Component misc
Context AsyncRoot
QWeb router
Store Link
useState RouteComponent
config Router
mode tags
core xml
EventBus utils
Observer debounce
hooks escape
onWillStart loadJS
onMounted loadFile
onWillUpdateProps shallowEqual
onWillPatch whenReady
onPatched
onWillUnmount
useContext
useState
useRef
useSubEnv
useStore
useDispatch
useGetters
Note that for convenience, the useState hook is also exported at the root of the owl object.