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

Support for ~~Fragment~~ and named slots #4

Open
JulianCataldo opened this issue Nov 13, 2022 · 0 comments
Open

Support for ~~Fragment~~ and named slots #4

JulianCataldo opened this issue Nov 13, 2022 · 0 comments

Comments

@JulianCataldo
Copy link
Contributor

JulianCataldo commented Nov 13, 2022

Hey there!

Actually, passing the Fragment component like this doesn't seems to work:

  <Markdown
    content={content}
    components={{
      // ...,
      Fragment,
      Tabs,
    }}
  />

In a MD:

<Fragment slot="tab-1">Tab 1</Fragment>

Fragment is skipped
Using a real elem. like div fixes this.
However named slots are not supported. The default one are working well.


EDIT:
Ok, I've done some test, and passing Fragment is effective, it's the named slots which are the culprit.

@JulianCataldo JulianCataldo changed the title Support for Fragment and named slots Support for ~~Fragment~~ and named slots Nov 13, 2022
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

No branches or pull requests

1 participant