You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Auro form components, such as auro-input, auro-dropdown, etc., are currently self-contained individual repositories.
Due to this component independence, it has become challenging to maintain separate repositories with numerous interconnected dependencies, complicating the ability to validate a release across related parent components.
Describe the solution you'd like
Consolidate all Auro form components into a new auro-form component, reducing the distributed complexity of the Auro form library.
Acceptance Criteria
Migrate auro-input into auro-form, beginning integration
Update postCss.mjs to search directories recursively & process CSS files with PostCSS
Update package.json scripts (such as sass:render) to search directories recursively
Disable SCSS Stylelint rules (Components will be updated with latest markup upon release)
Repo builds without error
Bundler compiles as expected
Confirm auro-form__bundled is generated, along with respective files for individual form components (auro-input__bundled, etc)
Create Doc page that renders auro-dropdown and auro-input
Migrate test files
Migrate postscripts (postCss.mjs, etc) back to Auro Library for future component generation
Investigate adding individual tests for components to package.json(exp: test:input)
Investigate whether all nested components should be built using dev / build at once, individually or optionally.
Update folder structure to incorporate new monorepo structure.
Patrick-Daly-AA
changed the title
auro-form: consolidate auro form components into a single component
auro-form: get Auro-input working as a form component in Auro-Form
Oct 3, 2024
chrisfalaska
changed the title
auro-form: get Auro-input working as a form component in Auro-Form
auro-form: get auro-input working as an integrated form component
Oct 3, 2024
Is your feature request related to a problem? Please describe.
Auro form components, such as
auro-input
,auro-dropdown
, etc., are currently self-contained individual repositories.Due to this component independence, it has become challenging to maintain separate repositories with numerous interconnected dependencies, complicating the ability to validate a release across related parent components.
Describe the solution you'd like
Consolidate all Auro form components into a new
auro-form
component, reducing the distributed complexity of the Auro form library.Acceptance Criteria
auro-input
intoauro-form
, beginning integrationpostCss.mjs
to search directories recursively & process CSS files with PostCSSpackage.json
scripts (such assass:render
) to search directories recursivelyauro-form__bundled
is generated, along with respective files for individual form components (auro-input__bundled
, etc)auro-dropdown
andauro-input
test
filespostCss.mjs
, etc) back to Auro Library for future component generationpackage.json
(exp:test:input
)dev
/build
at once, individually or optionally.package.json
scripts for new monorepo structure #12form
with new component registration logic & update input to latest version #21dropdown
component (styling, tests, etc.) #20package.json
back to Auro Library for future component generation #14auro-formkit
#35Additional context
No response
Exit criteria
No response
The text was updated successfully, but these errors were encountered: