Paul Gschwendtner e382632473 build: fix symbol extractor not dealing with ES2015 classes (#38093) ... We recently reworked our `ng_rollup_bundle` rule to no longer output ESM5 and to optimize applications properly (previously applications were not optimized properly due to incorrect build optimizer setup). This change meant that a lot of symbols have been removed from the golden correctly. See: fd65958b88 Unfortunately though, a few symbols have been accidentally removed because they are now part of the bundle as ES2015 classes which the symbol extractor does not pick up. This commit fixes the symbol extractor to capture ES2015 classes. We also update the golden to reflect this change. PR Close #38093		2020-07-16 13:54:23 -07:00
..
symbol_extractor_spec	build: fix symbol extractor not dealing with ES2015 classes (#38093)	2020-07-16 13:54:23 -07:00
BUILD.bazel	build: fix symbol extractor not dealing with ES2015 classes (#38093)	2020-07-16 13:54:23 -07:00
cli.ts	build: update license headers to reference Google LLC (#37205)	2020-05-26 14:26:58 -04:00
index.bzl	build: update license headers to reference Google LLC (#37205)	2020-05-26 14:26:58 -04:00
symbol_extractor.ts	build: fix symbol extractor not dealing with ES2015 classes (#38093)	2020-07-16 13:54:23 -07:00
symbol_extractor_spec.ts	build: fix symbol extractor not dealing with ES2015 classes (#38093)	2020-07-16 13:54:23 -07:00