mirror of
https://github.com/odoo/owl.git
synced 2025-10-06 19:59:41 +07:00
0931a4dc5b
Before this commit, the handlers were bound to the current context, which is often the component but not necessarily. In some cases, a sub scope can be created (with t-foreach, or slots, or t-call), and the context is actually an object with the actual component instance it its prototype chain, but not the component.
🦉 OWL Documentation 🦉
Reference
- Animations
- Component
- Concurrency Model
- Configuration
- Context
- Environment
- Event Bus
- Hooks
- Miscellaneous Components
- Observer
- Props
- Props Validation
- QWeb Templating Language
- QWeb Engine
- Router
- Store
- Tags
- Utils
Learning Resources
- Quick Start: create an (almost) empty Owl application
- Tutorial: create a TodoList application
- Testing Owl components
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 Portal
Store router
useState Link
config RouteComponent
mode Router
core tags
EventBus xml
Observer utils
hooks debounce
onWillStart escape
onMounted loadJS
onWillUpdateProps loadFile
onWillPatch shallowEqual
onPatched whenReady
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.