angular-docs-cn/integration/ivy-trusted-types
Bjarki c2298512b3 test(core): enforce Trusted Types in ivy-trusted-types integration test (#39614)
Enforce Trusted Types in the ivy-trusted-types integration test by
setting an appropriate CSP header in the project's angular.json.

PR Close #39614
2020-11-19 12:16:38 -08:00
..
e2e test(core): make ivy-trusted-types similar to other integration tests (#39614) 2020-11-19 12:16:36 -08:00
src
.browserslistrc
.editorconfig
.gitignore
README.md
angular.json test(core): enforce Trusted Types in ivy-trusted-types integration test (#39614) 2020-11-19 12:16:38 -08:00
karma.conf.js test(core): make ivy-trusted-types similar to other integration tests (#39614) 2020-11-19 12:16:36 -08:00
package.json test(core): make ivy-trusted-types similar to other integration tests (#39614) 2020-11-19 12:16:36 -08:00
tsconfig.app.json
tsconfig.json
tsconfig.spec.json
tslint.json
yarn.lock test(core): make ivy-trusted-types similar to other integration tests (#39614) 2020-11-19 12:16:36 -08:00

README.md

IvyTrustedTypes

This project was generated with Angular CLI version 11.0.0-rc.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.

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.

Further help

To get more help on the Angular CLI use ng help or go check out the Angular CLI Overview and Command Reference page.