Doug Parker e0a72857cc fix(bazel): construct a manifest file even when warnings are emitted (#43582) ... Refs #42966. Previously if _any_ diagnostics were emitted, regardless of their category, the manifest would not be generated. This means that if a target emits only warnings and no errors, it would still fail to build because it does not generate all the required output files (specifically the `.es5.MF` file). Now the manifest file is generated as long as there are no error diagnostics in the result. This makes `ng_module()` support compiler warnings as a user would expect. Added a test which uses extended template diagnostics to trigger the invalid banana in box diagnostic. This generates a warning and uses Skylib's `build_test()` to verify that it builds successfully. Unfortunately there is no easy way to verify that the warning diagnostic is emitted at all. `expected_diagnostics` should be able to do that, but it doesn't seem to have any effect on `ng_module()` and may not be integrated. Instead, testing that a target with warnings builds correctly is the best we can easily do here without a deeper investigation. PR Close #43582		2021-09-29 09:58:24 -07:00
..
ng_package	test(bazel): update example_package.golden (#42804)	2021-07-09 12:14:56 -07:00
ngc-wrapped	fix(bazel): construct a manifest file even when warnings are emitted (#43582)	2021-09-29 09:58:24 -07:00