Skip to content

docs: mention using v-slot directly on a component for a lone named slot - #3491

Open
ValentinYoushkevich wants to merge 1 commit into
vuejs:mainfrom
ValentinYoushkevich:docs/v-slot-named-slot-on-component
Open

ValentinYoushkevich wants to merge 1 commit into
vuejs:mainfrom
ValentinYoushkevich:docs/v-slot-named-slot-on-component

Conversation

@ValentinYoushkevich

Copy link
Copy Markdown

Description of Problem

The Slots guide and the v-slot API entry say a named slot needs a <template>, but the compiler also accepts v-slot on the component tag for a lone named slot (<MyComponent #header>…</MyComponent>), and vuejs/core covers it with the on component named slot test. Closes #2190.

Proposed Solution

Mention that form in the Named Slots section and in the API "Limited to" list. Mixing it with <template v-slot> children is still a compile error, as the guide already explains.

Additional Information

vuejs/eslint-plugin-vue#3192 waits on this before vue/valid-v-slot stops reporting the form.

@netlify

netlify Bot commented Nov 9, 2026 •

Copy link
Copy Markdown

✅ Deploy Preview for vuejs ready!

Name Link
🔨 Latest commit 99b9cca
🔍 Latest deploy log https://app.netlify.com/projects/vuejs/deploys/6af1a8398ca6c728a89ecc77
😎 Deploy Preview https://deploy-preview-3491--vuejs.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Using named slots directly on the component

1 participant