History

Miško Hevery 2e4d17f3a9 perf(core): make sanitization tree-shakable in Ivy mode (#31934 )

In VE the `Sanitizer` is always available in `BrowserModule` because the VE retrieves it using injection.

In Ivy the injection is optional and we have instructions instead of component definition arrays. The implication of this is that in Ivy the instructions can pull in the sanitizer only when they are working with a property which is known to be unsafe. Because the Injection is optional this works even if no Sanitizer is present. So in Ivy we first use the sanitizer which is pulled in by the instruction, unless one is available through the `Injector` then we use that one instead.

This PR does few things:
1) It makes `Sanitizer` optional in Ivy.
2) It makes `DomSanitizer` tree shakable.
3) It aligns the semantics of Ivy `Sanitizer` with that of the Ivy sanitization rules.
4) It refactors `DomSanitizer` to use same functions as Ivy sanitization for consistency.

PR Close #31934

2019-08-15 10:30:12 -07:00

bypass.ts

perf(core): make sanitization tree-shakable in Ivy mode (#31934 )

2019-08-15 10:30:12 -07:00

html_sanitizer.ts

feat(core): add missing ARIA attributes to html sanitizer (#29685 )

2019-04-25 12:30:55 -07:00

inert_body.ts

refactor: remove redundant error in catch (#25478 )

2019-01-04 15:42:19 -08:00

readme.md

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

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

sanitization.ts

perf(core): make sanitization tree-shakable in Ivy mode (#31934 )

2019-08-15 10:30:12 -07:00

sanitizer.ts

perf(core): make sanitization tree-shakable in Ivy mode (#31934 )

2019-08-15 10:30:12 -07:00

security.ts

perf(core): make sanitization tree-shakable in Ivy mode (#31934 )

2019-08-15 10:30:12 -07:00

style_sanitizer.ts

perf(core): make sanitization tree-shakable in Ivy mode (#31934 )

2019-08-15 10:30:12 -07:00

url_sanitizer.ts

refactor(core): update docs (#29600 )

2019-04-02 10:28:23 -07: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.