38806cbf99
Don't allow xls files #540 |
||
|---|---|---|
| docker | ||
| e2e | ||
| src | ||
| .browserslistrc | ||
| .editorconfig | ||
| .eslintrc.json | ||
| .gitignore | ||
| .sonarcloud.properties | ||
| .travis.yml | ||
| Dockerfile | ||
| README.md | ||
| angular.json | ||
| karma.conf.js | ||
| karma.globals.js | ||
| nginx.conf | ||
| package-lock.json | ||
| package.json | ||
| sonar-project.properties | ||
| tsconfig.json | ||
| webpack.config.js | ||
README.md
sartography/cr-connect-bpmn
CR Connect BPMN Configurator
This project was generated with Angular CLI version 7.1.1.
Development server
Run ng serve for a dev server. Navigate to http://localhost:4200/. The app will automatically reload if you change any of the source files.
You can also user npm run start:dev to get a dev server with lazy loading. This makes development much more efficient
Code scaffolding
Run ng generate component component-name to generate a new component. You can also use ng generate directive|pipe|service|class|guard|interface|enum|module.
Build
Run ng build to build the project. The build artifacts will be stored in the dist/ directory. Use the --prod flag for a production build.
Running unit tests
Run ng test to execute the unit tests via Karma.
Running end-to-end tests
Run ng e2e to execute the end-to-end tests via Protractor.
One way to check for coverage:
Install lcov (in ubuntu: sudo apt-get install lcov)
run ng test --no-watch --code-coverage to generate a coverage directory, with an lcov file in it
run genhtml coverage/lcov.info -o coverage/html to generate an html doc that looks at coverage (index.html)
Further help
To get more help on the Angular CLI use ng help or go check out the Angular CLI README.