This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
Move templates over into auro-library #423
Labels
not-reviewed
Issue has not been reviewed by Auro team members
Type: Feature
New Feature
wc-generator
General Support Request
We want to move most (if not all) templates that are currently living in the generator over into
auro-library
. We want to do this because we want users to be able to use the generator and generate a component, without having all of the Auro constraints on the newly generated component. A user then would be able to run a script fromauro-library
to add all of those Auro templates if they wanted them.Possible Solution
auro-library
auro-library
, resulting in only some templates transferredAdditional context
As part of moving the template files out of the generator the template must be updated to have a dev dependency of auro-library and incorporate a script into the package.json to run the scripting that incorporates all the Auro configuration files we have automated.
This will be a necessary step of creating a new auro component and the template should come out of the box ready to pull the configuration in via automation.
The text was updated successfully, but these errors were encountered: