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.

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

Auro-icon: Update component registration logic #144

Closed
sun-mota opened this issue Oct 16, 2024 · 0 comments · Fixed by #145
Closed

Auro-icon: Update component registration logic #144

sun-mota opened this issue Oct 16, 2024 · 0 comments · Fixed by #145
Assignees

Comments

@sun-mota
Copy link
Contributor

Please verify the version of auro-icon 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

Exit criteria

No response

@sun-mota sun-mota added Type: Bug Bug or Bug fixes auro-icon not-reviewed Issue has not been reviewed by Auro team members labels Oct 16, 2024
@sun-mota sun-mota self-assigned this Oct 16, 2024
@sun-mota sun-mota linked a pull request Oct 17, 2024 that will close this issue
6 tasks
sun-mota added a commit that referenced this issue Oct 21, 2024
AuroIcon.register is to easily register the element without extra importing
`import '@aurodesignsystem/auro-icon'` will still register this element to `<auro-icon>`
`import { AuroIcon } from '../src/auro-icon.js` wont register this element until `AuroIcon.register` gets called

Similarly, `AuroAlaska` now needs to be registered using `AuroAlaska.register` before you can use `<auro-alaska>,` if you're importing `auro-alaska.js`.
To skip the registration step, you can simply import `@aurodesignsystem/auro-icon`.
sun-mota added a commit that referenced this issue Oct 24, 2024
…ine <auro-icon> as a customElement #144

- Update dependency versions
- `AuroIcon.register` is to easily register the element without extra importing
- `import '@aurodesignsystem/auro-icon'` will still register this element to `<auro-icon>`
- `import { AuroIcon } from '../src/auro-icon.js` wont register this element until `AuroIcon.register` gets called
- Similarly, `AuroAlaska` now needs to be registered using `AuroAlaska.register` before you can use `<auro-alaska>,` if you're importing `auro-alaska.js`.
To skip the registration step, you can simply import `@aurodesignsystem/auro-icon`.
@jason-capsule42 jason-capsule42 removed Type: Bug Bug or Bug fixes not-reviewed Issue has not been reviewed by Auro team members labels Oct 27, 2024
jordanjones243 pushed a commit that referenced this issue Oct 28, 2024
…con> as a customElement #144

BREAKING CHANGE: `auro-alaska` must be registered to use the `src/auro-alaska.js` import.

- Update dependency versions
- `AuroIcon.register` is to easily register the element without extra importing
- `import '@aurodesignsystem/auro-icon'` will still register this element to `<auro-icon>`
- `import { AuroIcon } from '../src/auro-icon.js` wont register this element until `AuroIcon.register` gets called
- Similarly, `AuroAlaska` now needs to be registered using `AuroAlaska.register` before you can use `<auro-alaska>,` if you're importing `auro-alaska.js`.
To skip the registration step, you can simply import `@aurodesignsystem/auro-icon`.
jordanjones243 pushed a commit that referenced this issue Oct 28, 2024
…con> as a customElement #144

BREAKING CHANGE: `auro-alaska` must be registered to use the `src/auro-alaska.js` import.

- Update dependency versions
- `AuroIcon.register` is to easily register the element without extra importing
- `import '@aurodesignsystem/auro-icon'` will still register this element to `<auro-icon>`
- `import { AuroIcon } from '../src/auro-icon.js` wont register this element until `AuroIcon.register` gets called
- Similarly, `AuroAlaska` now needs to be registered using `AuroAlaska.register` before you can use `<auro-alaska>,` if you're importing `auro-alaska.js`.
To skip the registration step, you can simply import `@aurodesignsystem/auro-icon`.
blackfalcon pushed a commit that referenced this issue Oct 28, 2024
# [6.0.0](v5.0.2...v6.0.0) (2024-10-28)

### Bug Fixes

* change how we support custom size [#147](#147) ([5cbb375](5cbb375))

### Features

* add tag name as attribute when custom registered ([669997a](669997a))
* **api:** importing ./src/auro-icon.js will no longer define <auro-icon> as a customElement [#144](#144) ([353d5c3](353d5c3))

### Performance Improvements

* update deps ([2d91c53](2d91c53))
* update sweep npm script ([4f2a171](4f2a171))

### BREAKING CHANGES

* the old customSize attribute is no longer supported. See new documentation on API page under Theme Support.
* **api:** `auro-alaska` must be registered to use the `src/auro-alaska.js` import.

- Update dependency versions
- `AuroIcon.register` is to easily register the element without extra importing
- `import '@aurodesignsystem/auro-icon'` will still register this element to `<auro-icon>`
- `import { AuroIcon } from '../src/auro-icon.js` wont register this element until `AuroIcon.register` gets called
- Similarly, `AuroAlaska` now needs to be registered using `AuroAlaska.register` before you can use `<auro-alaska>,` if you're importing `auro-alaska.js`.
To skip the registration step, you can simply import `@aurodesignsystem/auro-icon`.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants