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

Update form with new component registration logic & update input to latest version #21

Closed
3 tasks done
Tracked by #1 ...
chrisfalaska opened this issue Oct 31, 2024 · 2 comments · Fixed by #39
Closed
3 tasks done
Tracked by #1 ...
Assignees

Comments

@chrisfalaska
Copy link
Contributor

chrisfalaska commented Oct 31, 2024

Update the form component to use the new component registration logic (example: AlaskaAirlines/auro-icon#144)

  • How will children components also take advantage of the custom registry (ie, input, dropdown, etc)?

Issues raised

@chrisfalaska chrisfalaska changed the title Update form with new component registry pattern Update form with new component registration pattern Oct 31, 2024
@chrisfalaska chrisfalaska changed the title Update form with new component registration pattern Update form with new component registration logic Oct 31, 2024
@sun-mota
Copy link
Contributor

sun-mota commented Nov 1, 2024

There is a dup: #13

@chrisfalaska chrisfalaska changed the title Update form with new component registration logic Update form with new component registration logic & update input to latest version Nov 4, 2024
sun-mota added a commit that referenced this issue Nov 5, 2024
- `AuroForm.register` is to easily register the element without extra importing
- `import '@aurodesignsystem/auro-form'` will still register this element to `<auro-form>`
- `import { AuroForm } from '../src/auro-form'` wont register this element until `AuroForm.register` gets called
sun-mota added a commit that referenced this issue Nov 5, 2024
- `AuroForm.register` is to easily register the element without extra importing
- `import '@aurodesignsystem/auro-form'` will still register this element to `<auro-form>`
- `import { AuroForm } from '../src/auro-form'` wont register this element until `AuroForm.register` gets called
sun-mota added a commit that referenced this issue Nov 5, 2024
- `AuroForm.register` is to easily register the element without extra importing
- `import '@aurodesignsystem/auro-form'` will still register this element to `<auro-form>`
- `import { AuroForm } from '../src/auro-form'` wont register this element until `AuroForm.register` gets called
sun-mota added a commit that referenced this issue Nov 6, 2024
- `AuroForm.register` is to easily register the element without extra importing
- `import '@aurodesignsystem/auro-form'` will still register this element to `<auro-form>`
- `import { AuroForm } from '../src/auro-form'` wont register this element until `AuroForm.register` gets called
sun-mota added a commit that referenced this issue Nov 7, 2024
- `AuroForm.register` is to easily register the element without extra importing
- `import '@aurodesignsystem/auro-form'` will still register this element to `<auro-form>`
- `import { AuroForm } from '../src/auro-form'` wont register this element until `AuroForm.register` gets called
sun-mota added a commit that referenced this issue Nov 12, 2024
- `AuroForm.register` is to easily register the element without extra importing
- `import '@aurodesignsystem/auro-form'` will still register this element to `<auro-form>`
- `import { AuroForm } from '../src/auro-form'` wont register this element until `AuroForm.register` gets called
sun-mota added a commit that referenced this issue Nov 12, 2024
- `AuroForm.register` is to easily register the element without extra importing
- `import '@aurodesignsystem/auro-form'` will still register this element to `<auro-form>`
- `import { AuroForm } from '../src/auro-form'` wont register this element until `AuroForm.register` gets called
sun-mota added a commit that referenced this issue Nov 14, 2024
- `AuroForm.register` is to easily register the element without extra importing
- `import '@aurodesignsystem/auro-form'` will still register this element to `<auro-form>`
- `import { AuroForm } from '../src/auro-form'` wont register this element until `AuroForm.register` gets called
sun-mota added a commit that referenced this issue Nov 14, 2024
- `AuroForm.register` is to easily register the element without extra importing
- `import '@aurodesignsystem/auro-form'` will still register this element to `<auro-form>`
- `import { AuroForm } from '../src/auro-form'` wont register this element until `AuroForm.register` gets called
@sun-mota sun-mota linked a pull request Nov 14, 2024 that will close this issue
sun-mota added a commit that referenced this issue Nov 21, 2024
- `AuroForm.register` is to easily register the element without extra importing
- `import '@aurodesignsystem/auro-form'` will still register this element to `<auro-form>`
- `import { AuroForm } from '../src/auro-form'` wont register this element until `AuroForm.register` gets called
sun-mota added a commit that referenced this issue Nov 25, 2024
- `AuroForm.register` is to easily register the element without extra importing
- `import '@aurodesignsystem/auro-form'` will still register this element to `<auro-form>`
- `import { AuroForm } from '../src/auro-form'` wont register this element until `AuroForm.register` gets called
sun-mota added a commit that referenced this issue Nov 25, 2024
- `AuroForm.register` is to easily register the element without extra importing
- `import '@aurodesignsystem/auro-form'` will still register this element to `<auro-form>`
- `import { AuroForm } from '../src/auro-form'` wont register this element until `AuroForm.register` gets called
sun-mota added a commit that referenced this issue Nov 25, 2024
- `AuroForm.register` is to easily register the element without extra importing
- `import '@aurodesignsystem/auro-form'` will still register this element to `<auro-form>`
- `import { AuroForm } from '../src/auro-form'` wont register this element until `AuroForm.register` gets called
jason-capsule42 pushed a commit that referenced this issue Nov 25, 2024
# [1.1.0](v1.0.1...v1.1.0) (2024-11-25)

### Bug Fixes

* fix stylelint error on dropdown ([0b1e274](0b1e274))

### Features

* add checkbox into components [#27](#27) ([3af6779](3af6779))
* add menu [#28](#28) ([2fe16fd](2fe16fd))
* **api:** add register static method [#21](#21) ([9953da2](9953da2))
* update input to 4.1.1 ([4b1d182](4b1d182))

### Performance Improvements

* update .stylelint to be same as generator's ([49adec0](49adec0))
* update auro-icon to `6.0.3` ([c586d37](c586d37))
* update stylelint and following changes on scss ([9fd61ab](9fd61ab))
* upgrade input to 4.1.3 ([433fb27](433fb27))
* upgrade input to 4.2.0 ([cbb6530](cbb6530))
rmenner pushed a commit that referenced this issue Dec 3, 2024
- `AuroForm.register` is to easily register the element without extra importing
- `import '@aurodesignsystem/auro-form'` will still register this element to `<auro-form>`
- `import { AuroForm } from '../src/auro-form'` wont register this element until `AuroForm.register` gets called
rmenner pushed a commit that referenced this issue Dec 3, 2024
* fix stylelint error on dropdown ([0b1e274](0b1e274))

* add checkbox into components [#27](#27) ([3af6779](3af6779))
* add menu [#28](#28) ([2fe16fd](2fe16fd))
* **api:** add register static method [#21](#21) ([9953da2](9953da2))
* update input to 4.1.1 ([4b1d182](4b1d182))

* update .stylelint to be same as generator's ([49adec0](49adec0))
* update auro-icon to `6.0.3` ([c586d37](c586d37))
* update stylelint and following changes on scss ([9fd61ab](9fd61ab))
* upgrade input to 4.1.3 ([433fb27](433fb27))
* upgrade input to 4.2.0 ([cbb6530](cbb6530))
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants