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
Hi,
It would be very useful if you could add a workspace-specific schematics use case example in Readme.
Maybe we just have to follow the angular schematics docs ?
The text was updated successfully, but these errors were encountered:
@llioss nx is extending angular-cli. Workspace-specific schematics are still using ng generate libs... syntax. Only few doesn't exist on cli, like ngrx and affected.
You can get a list of the nx specific commands by running:
I'm in the same boat, looking at creating some space-specific schematics that extend the ones provided by Nx but finding it hard to get started with the minimal documentation available in the docs.
For example:
Once the schematic is generated, how do we register / call it, the screenshot in that doc doesn't show the executed command?
How would we extend the "lib" schematic to tweak a file that is generated, for example adding ci-specific config into the karma.conf.js?
Hi,
It would be very useful if you could add a workspace-specific schematics use case example in Readme.
Maybe we just have to follow the angular schematics docs ?
The text was updated successfully, but these errors were encountered: