From a2ea2ec615b4744b9689302b192bb486d9efc799 Mon Sep 17 00:00:00 2001
From: Uaena_Alex_John <63441399+13RTK@users.noreply.github.com>
Date: Thu, 11 Sep 2025 22:48:09 +0800
Subject: [PATCH] docs: Update outputs.md to demonstrate how to use event data
 (#63732) PR Close #63732

---
 adev/src/content/guide/components/outputs.md | 14 ++++++++++++++
 1 file changed, 14 insertions(+)

diff --git a/adev/src/content/guide/components/outputs.md b/adev/src/content/guide/components/outputs.md
index ad8bbcacc70..16593b447ff 100644
--- a/adev/src/content/guide/components/outputs.md
+++ b/adev/src/content/guide/components/outputs.md
@@ -52,6 +52,20 @@ When defining an event listener in a template, you can access the event data fro
 <custom-slider (valueChanged)="logValue($event)" />
 ```
 
+Receive the event data in the parent component:
+
+<docs-code language="ts" highlight="">
+@Component({
+ /*...*/
+})
+export class App {
+  logValue(value: number) {
+    ...
+  }
+}
+
+</docs-code>
+
 ## Customizing output names
 
 The `output` function accepts a parameter that lets you specify a different name for the event in a template: