crisbeto 6d534f10e6 fix(ivy): don't run decorator handlers against declaration files (#34557) ... Currently the decorator handlers are run against all `SourceFile`s in the compilation, but we shouldn't be doing it against declaration files. This initially came up as a CI issue in #33264 where it was worked around only for the `DirectiveDecoratorHandler`. These changes move the logic into the `TraitCompiler` and `DecorationAnalyzer` so that it applies to all of the handlers. PR Close #34557		2020-01-10 15:54:51 -08:00
..
integrationtest	Revert "refactor: handle breaking changes in rules_nodejs 1.0.0 (#34589)" (#34730)	2020-01-10 14:12:15 -08:00
ngcc	fix(ivy): don't run decorator handlers against declaration files (#34557)	2020-01-10 15:54:51 -08:00
src	fix(ivy): don't run decorator handlers against declaration files (#34557)	2020-01-10 15:54:51 -08:00
test	Revert "refactor: handle breaking changes in rules_nodejs 1.0.0 (#34589)" (#34730)	2020-01-10 14:12:15 -08:00
BUILD.bazel	Revert "build: upgrade to rules_nodejs 1.0.0 (first stable release) (#34589)" (#34730)	2020-01-10 14:12:15 -08:00
index.ts	refactor(compiler-cli): Move diagnostics files to language service (#33809)	2019-11-14 09:29:07 -08:00
package.json	build: set up all packages to publish via wombot proxy (#33747)	2019-11-13 11:34:33 -08:00
tsconfig-build.json	build: reference zone.js from source directly instead of npm. (#33046)	2019-11-06 00:48:34 +00:00
tsconfig.json	perf(ivy): ngcc - only find dependencies when targeting a single entry-point (#30525)	2019-07-09 09:40:46 -07:00