igniteui-cli
igniteui-cli copied to clipboard
IgniteUI
Ignite UI Command-Line Interface by Infragistics
## Is your feature request related to a problem? Please describe. Currently, each added view brings it's own component registration:   Thankfully, the Ignite UI Web Components method guards...
### 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,...
### Description Our utils function `Util.lowerDashed` does not properly generate a dashed name from a CamelCased input. - Ignite UI CLI version: 6.0.0 - Framework: N/A ### Steps to reproduce...
### Description Currently imports are missing file extension, resulting in lint errors. TypeScriptFileUpdate.ts should be updated to generate the imports inside app-routing.ts with .js extensions - Ignite UI CLI version:...
### Description Currently web components projects use own TypeScriptFileUpdate.ts file, located inside their own folder. It duplicates much of the logic inside the "general" file placed under "packages/core/typescript". All projects...
### Description We can add a 'hidden' option to the CLI instead where it won't replace the project name at all (or since schematics will likely complain - maybe try...
Additional information related to this pull request: - [x] seperate app.module.ts - [ ] each component index.ts should define needed modules - [ ] typescriptfileupdate for WC extends angular one...
### Description A number of packages listed as dev dependencies in the Angular project's package.json are unused - such as `codelyzer` which was dropped in the switch to eslint I...
Instead of Default and Custom themes, allow users to choose between the 8 predefined themes and implement them as part of the style.scss file.
