Skip to content

Commit d971b8e

Browse files
authored
fix
1 parent c76dd1c commit d971b8e

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

src/LiveComponent/doc/index.rst

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -182,33 +182,33 @@ let's keep going because… things get cooler.
182182
a ``mount()`` method or use the ``PostMount`` hook: `Twig Component mount documentation`_.
183183

184184
Hooks: Handle Component Behavior
185-
----------------------------------------
185+
--------------------------------
186186
Most of the time, you'll just pass data to your components and
187187
let it handle the rest. However, if you need to do something
188188
more complex during certain stages of a component's lifecycle, you
189189
can take advantage of lifecycle hooks.
190190

191191
``PostHydrate`` Hook
192-
~~~~~~~~~~~~~~~~~~~
192+
~~~~~~~~~~~~~~~~~~~~
193193
The ``#[PostHydrate]`` hook is called immediately after the component's state
194194
is loaded from the client. This is useful if you need to process or adjust
195195
the data once it’s been hydrated.
196196

197197
``PreDehydrate`` Hook
198-
~~~~~~~~~~~~~~~~~~~
198+
~~~~~~~~~~~~~~~~~~~~~
199199
The ``#[PreDehydrate]`` hook is triggered just before your component’s state
200200
is sent back to the client. You can use this to modify or clean up the data
201201
before it’s serialized and returned to the client.
202202

203203
``PreReRender`` Hook
204-
~~~~~~~~~~~~~~~~~~~
204+
~~~~~~~~~~~~~~~~~~~~
205205
The ``#[PreReRender]`` hook is called before your component is re-rendered
206206
during an HTTP request. It does not run during the initial render but is
207207
helpful when you need to adjust the state before sending it back to
208208
the client for re-rendering.
209209

210210
Hook Priority
211-
~~~~~~~~~~~~~~~~~~~
211+
~~~~~~~~~~~~~
212212
You can control the order in which hooks are executed by using the ``priority``
213213
argument. If multiple hooks of the same type are registered in a component, those
214214
with a higher priority value will run first. This allows you to manage the order

0 commit comments

Comments
 (0)