2a1ff17b42
This commit runs tslint --fix with the angular/angular tslint configuration on the files inside the devtools codebase. Notably, the file-header rule in `tslint.json` was missing a default attribute. This commit adds that default attribute and sets it to the license header that is present in all files in this repo. After running tslint --fix with this default added, this commit added the license header to all files in the devtools directory. Note for the reviewer: the automatically added license headers were added as comments with the "/*!" prefix. Since we want these comments removed in builds, and the rest of the codebase uses "/**", a simple find and replace was performed on the devtools directory to change these prefixes to "/**". |
||
|---|---|---|
| .. | ||
| src | ||
| BUILD.bazel | ||
| index.ts | ||
| karma.conf.js | ||
| ng-package.json | ||
| package.json | ||
| README.md | ||
| tsconfig.lib.json | ||
| tsconfig.lib.prod.json | ||
| tsconfig.spec.json | ||
| tslint.json | ||
ng-devtools
This library was generated with Angular CLI version 9.0.0-rc.5.
Code scaffolding
Run ng generate component component-name --project ng-devtools to generate a new component. You can also use ng generate directive|pipe|service|class|guard|interface|enum|module --project ng-devtools.
Note: Don't forget to add
--project ng-devtoolsor else it will be added to the default project in yourangular.jsonfile.
Build
Run ng build ng-devtools to build the project. The build artifacts will be stored in the dist/ directory.
Publishing
After building your library with ng build ng-devtools, go to the dist folder cd dist/ng-devtools and run npm publish.
Running unit tests
Run ng test ng-devtools to execute the unit tests via Karma.
Further help
To get more help on the Angular CLI use ng help or go check out the Angular CLI README.