Skip to content

Commit 4d65ec7

Browse files
committed
docs: removed non-existing return value from onLoop example
1 parent 91e047a commit 4d65ec7

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

docs/api/composables.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -13,13 +13,13 @@ The `useRenderLoop` composable is the core of **TresJS** animations. It allows y
1313
```ts
1414
const { onLoop, resume } = useRenderLoop()
1515

16-
onLoop(({ delta, elapsed, clock, dt }) => {
16+
onLoop(({ delta, elapsed, clock }) => {
1717
// I will run at every frame ~60FPS (depending of your monitor)
1818
})
1919
```
2020

2121
::: warning
22-
Be mindfull of the performance implications of using this composable. It will run at every frame, so if you have a lot of logic in your callback, it might impact the performance of your app. Specially if you are updating reactive states or references.
22+
Be mindful of the performance implications of using this composable. It will run at every frame, so if you have a lot of logic in your callback, it might impact the performance of your app. Specially if you are updating reactive states or references.
2323
:::
2424

2525
The `onLoop` callback receives an object with the following properties based on the [THREE clock](https://threejs.org/docs/?q=clock#api/en/core/Clock):

0 commit comments

Comments
 (0)