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.

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

Handle more complex ContentSlot #44

Open
Atinux opened this issue Dec 6, 2022 — with Volta.net · 2 comments
Open

Handle more complex ContentSlot #44

Atinux opened this issue Dec 6, 2022 — with Volta.net · 2 comments
Labels
enhancement New feature or request

Comments

Copy link
Member

Atinux commented Dec 6, 2022

@Atinux Atinux added the enhancement New feature or request label Dec 6, 2022 — with Volta.net
@Tahul
Copy link
Contributor

Tahul commented Dec 20, 2022

@Atinux ; what do you think would be the best way to resolve this?

h('span', h(resolveComponent('ContentSlot'), { use: () => item }))

There is no real "proper" way to parse such usage.. except maybe if I only detect h(resolveComponent('ContentSlot')) as default slot in response?

That would kind of mean we only do support default slots for such usage?

If that's fine, I can make that change.

@stafyniaksacha
Copy link
Collaborator

@Tahul I think it's related to this: vuejs/rfcs#192

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants