Auro-popover: Update component registration logic #82
Assignees
Labels
Comments
sun-mota
added
Type: Bug
sun-mota
added a commit
that referenced
this issue
Oct 23, 2024
- Update dependency versions
- `AuroPopover.register` is to easily register the element without extra importing
- `import "@aurodesignsystem/auro-popover"` will still register this element to <auro-popover>
- `import { AuroPopover } from '../src/auro-popover` wont register this element until `AuroPopover.register` gets called
- Fixed the typo on Recommended Use and Version Control: `clement` -> `element`
6 tasks
6 tasks
jason-capsule42
removed
Type: Bug
sun-mota
added a commit
that referenced
this issue
Oct 23, 2024
- Update dependency versions
- `AuroPopover.register` is to easily register the element without extra importing
- `import "@aurodesignsystem/auro-popover"` will still register this element to <auro-popover>
- `import { AuroPopover } from '../src/auro-popover` wont register this element until `AuroPopover.register` gets called
- Fixed the typo on Recommended Use and Version Control: `clement` -> `element`
blackfalcon
pushed a commit
that referenced
this issue
Oct 23, 2024
# [4.1.0](v4.0.1...v4.1.0) (2024-10-23) ### Features * **api:** add register static method [#82](#82) ([2ac3681](2ac3681))
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Please verify the version of auro-popover 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.jsReproducing the error
None
Expected behavior
No response
What browsers are you seeing the problem on?
No response
Additional context
No response
Exit criteria
No response
The text was updated successfully, but these errors were encountered: