Update component registration logic #265
Assignees
Labels
auro-datepicker
not-reviewed
Issue has not been reviewed by Auro team members
Type: Bug
Bug or Bug fixes
Comments
sun-mota
added
auro-datepicker
not-reviewed
|
blocked by AlaskaAirlines/auro-library#70 |
|
Will move forward without supporting custom calendar modules. |
6 tasks
6 tasks
sun-mota
added a commit
that referenced
this issue
Oct 21, 2024
`AuroDatepicker.register` is to easily register the element without extra importing
`import '@aurodesignsystem/auro-datepicker'` will still register this element to `<auro-datepicker>`
`import { AuroDatepicker } from '../src/auro-datepicker.js'` wont register this element until `AuroDatepicker.register` gets called
sun-mota
added a commit
that referenced
this issue
Oct 21, 2024
`AuroDatepicker.register` is to easily register the element without extra importing
`import '@aurodesignsystem/auro-datepicker'` will still register this element to `<auro-datepicker>`
`import { AuroDatepicker } from '../src/auro-datepicker.js'` wont register this element until `AuroDatepicker.register` gets called
sun-mota
added a commit
that referenced
this issue
Oct 24, 2024
`AuroDatepicker.register` is to easily register the element without extra importing
`import '@aurodesignsystem/auro-datepicker'` will still register this element to `<auro-datepicker>`
`import { AuroDatepicker } from '../src/auro-datepicker.js'` wont register this element until `AuroDatepicker.register` gets called
blackfalcon
pushed a commit
that referenced
this issue
Oct 24, 2024
# [3.1.0](v3.0.2...v3.1.0) (2024-10-24) ### Bug Fixes * add file extension for proper ESM support ([46c5b74](46c5b74)) * add missing file extensions on imports ([66bd441](66bd441)) ### Features * **api:** add register static method [#265](#265) ([036e7d0](036e7d0)) ### Performance Improvements * update dependency versions ([773d9a8](773d9a8))
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Please verify the version of auro-datepicker 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
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: