JoostK 4f8eaac7ff fix(core): do not use Function constructors in development mode to avoid CSP violations (#43587) ... This commit removes the dynamic creation of named arrays for internal runtime storage arrays as they may cause CSP violations in development mode, when an application's CSP configuration does not include `unsafe-eval`. Named arrays for view data can still be enabled in development mode using the `ngDevMode=namedConstructors` query parameter when loading the application. The usage of native class syntax for named arrays does not have the desired effect when the code is downleveled to ES5. Since ES5 targets are becoming increasingly more rare this is considered less of a problem than the CSP violation. Fixes #43494 PR Close #43587		2021-11-09 18:02:13 +00:00
..
global	build: update license headers to reference Google LLC (#37205)	2020-05-26 14:26:58 -04:00
schematics	refactor(core): set up structure for google3 usage of migration schematics (#43980)	2021-11-04 11:23:12 -07:00
src	fix(core): do not use Function constructors in development mode to avoid CSP violations (#43587)	2021-11-09 18:02:13 +00:00
test	fix(core): do not use Function constructors in development mode to avoid CSP violations (#43587)	2021-11-09 18:02:13 +00:00
testing	fix(core): don't rethrow errors if test teardown has been disabled (#43635)	2021-10-04 17:31:26 -07:00
BUILD.bazel	refactor: remove entry_point attribute from ng_package targets (#43431)	2021-10-01 18:28:42 +00:00
index.ts	refactor(core): made comment structure consistent in index.ts (#43684)	2021-10-21 18:39:58 +00:00
package.json	refactor(compiler-cli): update peerDependencies to require rxjs ^7.4.0 (#43748)	2021-10-06 15:57:59 -07:00
PACKAGE.md	docs: add package doc files (#26047)	2018-10-05 15:42:14 -07:00
public_api.ts	build: update license headers to reference Google LLC (#37205)	2020-05-26 14:26:58 -04:00