Files

T

Igor Minar 03d47d5701 feat(core): manually annotate de-sugarred core tree-shakable providers with @pureOrBreakMyCode (#41096 )

This is necessary for closure compiler in order to support cross chunk code motion.

I'm intentionally not annotating these call sites with @__PURE__ at the moment because
build-optimizer does it within the Angular CLI build. In the future we might want to consider
having both annotations here in case we change how build-optimizer works.

PR Close #41096

2021-03-08 10:30:08 -08:00

bypass.ts

docs: update links to use HTTPS as protocol (#39718 )

2020-11-20 12:52:16 -08:00

html_sanitizer.ts

perf(core): use ngDevMode to tree-shake warnings (#39959 )

2020-12-04 10:21:36 -08:00

inert_body.ts

fix(core): ensure sanitizer works if DOMParser return null body (#40107 )

2021-01-06 10:32:24 -08:00

readme.md

refactor(core): move sanitization into core (#22540 )

2018-03-07 18:24:06 -08:00

sanitization.ts

refactor(core): express trusted constants with tagged template literals (#40082 )

2021-01-05 13:56:57 -08:00

sanitizer.ts

feat(core): manually annotate de-sugarred core tree-shakable providers with @pureOrBreakMyCode (#41096 )

2021-03-08 10:30:08 -08:00

security.ts

build: update license headers to reference Google LLC (#37205 )

2020-05-26 14:26:58 -04:00

url_sanitizer.ts

perf(core): use ngDevMode to tree-shake warnings (#39959 )

2020-12-04 10:21:36 -08:00

readme.md

Sanitization

This folder contains sanitization related code.

History

It used to be that sanitization related code used to be in @angular/platform-browser since it is platform related. While this is true, in practice the compiler schema is permanently tied to the DOM and hence the fact that sanitizer could in theory be replaced is not used in practice.

In order to better support tree shaking we need to be able to refer to the sanitization functions from the Ivy code. For this reason the code has been moved into the @angular/core.