-
Notifications
You must be signed in to change notification settings - Fork 4
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
Update component registration logic #342
Labels
Comments
6 tasks
6 tasks
sun-mota
added a commit
that referenced
this issue
Oct 21, 2024
AuroInput.register is to easily register the element without extra importing `import "@aurodesignsystem/auro-input"` will still register this element to <auro-input> `import { AuroInput } from '../src/auro-input.js` wont register this element until AuroInput.register gets called
sun-mota
added a commit
that referenced
this issue
Oct 24, 2024
AuroInput.register is to easily register the element without extra importing `import "@aurodesignsystem/auro-input"` will still register this element to <auro-input> `import { AuroInput } from '../src/auro-input.js` wont register this element until AuroInput.register gets called
blackfalcon
pushed a commit
that referenced
this issue
Oct 31, 2024
rmenner
pushed a commit
that referenced
this issue
Oct 31, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Please verify the version of auro-input you have installed
No response
Please describe the bug
Default import of index.js should register the default custom element only.
import of the component class should not register the custom element at all.
Remove all registration of custom-${component name} from the JS and only register as part of ./demo/index.js
Reproducing the error on the docsite
None
Expected behavior
No response
What browsers are you seeing the problem on?
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: