IgniteUI
[IgxSchematics] Angular Projects do not properly account for generate project prefix
Description
When calling ng new, you can specify a project prefix, which will be written in the generated project's angular.json and later be used for component generation.
For example, a project with prefix cool would have all component selectors starting w/ cool-<% component-name %>.
We are currently not handling this accordingly in a couple of ways:
We are not taking into account the project prefix in our angular templates (app is hardcoded)
We are relying on the project prefix to get the main project directory (src/app) where in really, we should not (it is hardcoded to src/app in Angular's CLI)
- Ignite UI CLI version: 6.1.0
- Framework: Angular
- Project type: igx-ts
Solutions
We should implement a similar function to this one for getting the project default path. This should be exposed in the public API. We should go over our templates and make a config entry for the app prefix, which in turn will be used in the component selectors.
