From 9927c6a127bf5c23782340129596e366bb3413f5 Mon Sep 17 00:00:00 2001
From: Eduardo San Martin Morote <posva13@gmail.com>
Date: Mon, 23 Oct 2023 20:52:04 +0200
Subject: [PATCH] docs: add example about passing props
MIME-Version: 1.0
Content-Type: text/plain; charset=utf8
Content-Transfer-Encoding: 8bit

Co-authored-by: Björn Harrtell <bjornharrtell@users.noreply.github.com>
---
 packages/docs/guide/essentials/passing-props.md | 17 +++++++++++++++++
 1 file changed, 17 insertions(+)

diff --git a/packages/docs/guide/essentials/passing-props.md b/packages/docs/guide/essentials/passing-props.md
index 56631771..c1b2d21c 100644
--- a/packages/docs/guide/essentials/passing-props.md
+++ b/packages/docs/guide/essentials/passing-props.md
@@ -78,3 +78,20 @@ const routes = [
 The URL `/search?q=vue` would pass `{query: 'vue'}` as props to the `SearchUser` component.
 
 Try to keep the `props` function stateless, as it's only evaluated on route changes. Use a wrapper component if you need state to define the props, that way Vue can react to state changes.
+
+## Via RouterView
+
+You can also pass any props directly via `<RouterView>`:
+
+```vue-html
+<RouterView v-slot="{ Component }">
+  <component
+    :is="Component"
+    view-prop="value"
+   />
+</RouterView
+```
+
+::: warning
+In this case, **all view components** will receive `view-prop`. This is usually not a good idea as  it means that all of the view components have declared a `view-prop` prop, which is not necessarily true. If possible, use any of the options above.
+:::
-- 
2.47.2