You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/guide/components/events.md
+1-4Lines changed: 1 addition & 4 deletions
Original file line number
Diff line number
Diff line change
@@ -292,13 +292,10 @@ export default {
292
292
## Events as Props {#events-props}
293
293
294
294
You may also declare and pass `events` as `props`, by prefixing the capitalized event name with `on`
295
-
296
-
:::info
297
295
Using `props.onEvent` has a different behaviour than using `emit('event')`, as the former will pass only handle the property based listener (either `@event` or `:on-event`)
298
-
:::
299
296
300
297
:::warning
301
-
If both `:onEvent` and `@event` are passed `props.onEvent` might be an array of `functions` instead of `function`.
298
+
If both `:onEvent` and `@event` are passed `props.onEvent` might be an array of `functions` instead of `function`, this behavior is not stable and might change in the future.
302
299
:::
303
300
304
301
Because of this, it is recommended to use `emit('event')` instead of `props.onEvent` when emitting events.
0 commit comments