Pete Bacon Darwin a827bc2e3a refactor(ivy): ngcc - mark target entry-point as processed even if ngcc was a noop (#29092) ... If `targetEntryPointPath` is provided to `mainNgcc` then we will now mark all the `propertiesToConsider` for that entry-point if we determine that it does not contain code that was compiled by Angular (for instance it has no `...metadata.json` file). The commit also renames `__modified_by_ngcc__` to `__processed_by_ivy_ngcc__`, since there may be entry-points that are marked despite ngcc not actually compiling anything. PR Close #29092		2019-03-20 14:45:55 -04:00
..
analysis	refactor(ivy): move ngcc into a higher level folder (#29092)	2019-03-20 14:45:54 -04:00
helpers	refactor(ivy): ngcc - simplify `Transformer.transform` API (#29092)	2019-03-20 14:45:54 -04:00
host	fix(ivy): ngcc - teach Esm5ReflectionHost about aliased variables (#29092)	2019-03-20 14:45:55 -04:00
integration	refactor(ivy): ngcc - mark target entry-point as processed even if ngcc was a noop (#29092)	2019-03-20 14:45:55 -04:00
packages	refactor(ivy): ngcc - mark target entry-point as processed even if ngcc was a noop (#29092)	2019-03-20 14:45:55 -04:00
rendering	refactor(ivy): ngcc - simplify `Transformer.transform` API (#29092)	2019-03-20 14:45:54 -04:00
BUILD.bazel	build(ivy): ngcc - only test under `no-ivy-aot` mode (#29092)	2019-03-20 14:45:54 -04:00