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.

Sign up for GitHub

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

Jump to bottom

Cross-component naming interference #315

Closed
G1tHappens opened this issue Jun 19, 2023 · 0 comments
Closed

Cross-component naming interference #315

G1tHappens opened this issue Jun 19, 2023 · 0 comments
Labels
bug Something isn't working

Comments

@G1tHappens
Copy link

Version

@nuxthq/ui: @nuxthq/ui: 2.4.0+
nuxt: 3.5.3

Reproduction Link

https://stackblitz.com/edit/nuxtlabs-ui-z4g2sk

Steps to reproduce

  • Create a custom component with the same name as an existing component in headlessUI
  • Use the NuxtUI component that uses the headlessUI component with the exact name.

What is Expected?

Components should render normally.

What is actually happening?

HeadlessUI component is replaced by the custom component.
@G1tHappens G1tHappens added the bug Something isn't working label Jun 19, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@G1tHappens