Lifecycle Methods
Overview
CBWIRE provides lifecycle methods you can hook into to update and render your components.
Order Of Operations
The lifecycle methods are executed in the following order when a component is initially loaded:
onMount()
onRender()
Lifecycle methods are executed in this order for subsequent AJAX requests.
onHydrate[DataProperty]()
onHydrate()
onUpdate[DataProperty]()
onUpdate()
Fire actions
onRender()
Methods
onMount
It runs only once when a component is initially wired. This can inject data values into your component via params you pass in when calling wire(), or pulling in values from the RC or PRC scopes.
onMount() only fires when the component is initially rendered and does not fire on subsequent requests when your component re-renders. This can cause issues referencing things such as the RC or PRC scope. If you pass in values with the RC or PRC scope, you must store them as data properties to ensure they are available to your component in subsequent requests.
onRender
It runs on all requests before rendering your component. This gives you more control if needed when rendering. There is also a renderIt() alias, which does the same.
onHydrate
Runs on subsequent requests after a component is hydrated but before computed properties are rendered, before a data property is updated or action is performed, or before the component is rendered.
onHydrate[ Property ]
Runs on subsequent requests after a specific data property is hydrated but before computed properties are rendered, before an action is performed, or before the component is rendered.
onUpdate
Runs on subsequent requests after any data property is updated using wire:model or $set.
onUpdate() will only fire if the incoming request updates a single data property, such as when using wire:model.
onUpdate[ Property ]
Runs on subsequent requests after a data property is updated using wire:model or $set. It only runs when the targeted data property is updated.
Last updated