Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

docs: suggest using <NuxtPage> rather than <RouterView> #25106

Merged
merged 2 commits into from
Jan 9, 2024
Merged

docs: suggest using <NuxtPage> rather than <RouterView> #25106

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
7afee4b
docs: describe the problem of using `<RouterView>` rather than `<Nuxt…
toto6038 Jan 8, 2024
145efb3
docs: fix typo
toto6038 Jan 9, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
4 changes: 4 additions & 0 deletions docs/3.api/1.components/2.nuxt-page.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,6 +15,10 @@ links:
It accepts same `name` and `route` props.
::

::callout{color="amber" icon="i-ph-warning-duotone"}
`<NuxtPage>` should be used instead of `<RouterView>` as the former takes additional care on internal states. Otherwise, `useRoute()` may return incorrect paths.
::

## Props

- `name`: tells `RouterView` to render the component with the corresponding name in the matched route record's components option.
Expand Down