angular/packages/bazel
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
..
docs refactor(bazel): remove old Angular CLI schematics and builder (#41575) 2021-04-13 13:01:59 -07:00
src fix(bazel): construct a manifest file even when warnings are emitted (#43582) 2021-09-29 09:58:24 -07:00
test fix(bazel): construct a manifest file even when warnings are emitted (#43582) 2021-09-29 09:58:24 -07:00
third_party/github.com/bazelbuild/bazel/src/main/protobuf build: upgrade angular build, integration/bazel and @angular/bazel package to rule_nodejs 2.2.0 (#39182) 2020-10-08 11:54:59 -07:00
BUILD.bazel refactor(bazel): remove old Angular CLI schematics and builder (#41575) 2021-04-13 13:01:59 -07:00
index.bzl build: emit performance JSON file for each ng_module() (#41125) 2021-03-24 13:42:25 -07:00
package.json feat(core): support TypeScript 4.4 (#43281) 2021-09-23 14:49:19 -07:00