-
-
Notifications
You must be signed in to change notification settings - Fork 174
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
Bug: Component's name that's a prefix of another can't be nested #530
Comments
Hi @desiprisg , I think you should adjust the indentation of the components you've added. Here is an example with the same case that I've already created. |
@alfianyusufabdullah The issue appears when the nested component has a different name (prefixed by the first component's name). Try naming the second one |
quantizor
added a commit
that referenced
this issue
Mar 21, 2024
quantizor
added a commit
that referenced
this issue
Mar 21, 2024
Innei
pushed a commit
to Innei/markdown-to-jsx
that referenced
this issue
Mar 28, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Noticed this while implementing an
<Accordion />
. I've added overrides for<Accordion />
and<AccordionItem />
and it seems that when nesting these, the outside element is not placed correctly.Simplified example:
will yield:
If
Accordion
was not a prefix ofAccordionItem
, this would work as expected.The text was updated successfully, but these errors were encountered: