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
{{ message }}
This repository was archived by the owner on Apr 4, 2025. It is now read-only.
But I don't think we can add functionality upon this
Mention any other details that might be useful
USE CASE:
Example: I want to create a schematic that would be running like ng new angular-jest --collection jest_collection_name"
and it would create a new angular project using @schematics/angular, and then add more files that would make this application support running tests using jest.
The text was updated successfully, but these errors were encountered:
create aliases for all angular schematics in your own collection (note that alias for just application is not enough since it in turn uses other schematics). then from your own custom schematic return something like this: export default function (options: any): Rule { return chain([ schematic('application', { style: 'scss', routing: true, directory: options.name, name: options.name }), mergeWith(apply(url('./files'), [ template({ name: options.name, }), ])), ]);
Bug Report or Feature Request (mark with an
x
)Area
Desired functionality
Right now I know we can do something like
But I don't think we can add functionality upon this
Mention any other details that might be useful
USE CASE:
Example: I want to create a schematic that would be running like
ng new angular-jest --collection jest_collection_name"
and it would create a new angular project using
@schematics/angular
, and then add more files that would make this application support running tests using jest.The text was updated successfully, but these errors were encountered: