Named slots in `<ContentSlot>` does not work when using `unwrap` - Githubissues

nuxt / content

The file-based CMS for your Nuxt application, powered by Markdown and Vue components.

https://content.nuxt.com

MIT License

3.08k stars 624 forks source link

Named slots in `<ContentSlot>` does not work when using `unwrap` #2523

Closed stafyniaksacha closed 8 months ago

stafyniaksacha commented 8 months ago

Environment

Operating System: Linux
Node Version: v18.18.0
Nuxt Version: 3.9.3
CLI Version: 3.10.0
Nitro Version: 2.8.1
Package Manager: npm@10.2.3
Builder: -
User Config: devtools, modules, content
Runtime Modules: @nuxt/content@2.11.0
Build Modules: -

Reproduction

https://stackblitz.com/edit/nuxt-starter-jwcdnr?file=content%2Findex.md,components%2Fcontent%2Ftest.vue

Describe the bug

Since 2.11, when we use <ContentSlot unwrap="p" :use="$slots.named" /> it renders the default slot instead of the named one.

The named slot is detected when we remove the unwrap property (<ContentSlot :use="$slots.named" />)

Additional context

No response

Logs

No response