angular-cn/dev-infra/bazel
Paul Gschwendtner 56bd21de6f feat(dev-infra): introduce shared tool for validating API signature (#42688)
For the last years the Angular repositories relied on `ts-api-guardian`
for testing the public API signature. This project worked well in
general but its another inconvenience to maintain if we could rely on
Microsoft's `api-extractor` tool.

Especially since with TypeScript 4.3 issues with export aliases appeared
that would require us to extend TS API guardian to support such exports.
This is not as straightforward as it sounds, given it requires rewriting
of declarations to show-case the proper name in the API golden. Microsoft's
API extractor has integrated support for this.

As of TypeScript 4.3, we want to start using the new `override` keyword.
We are not able to use that keyword currently because an old version of
API extractor is used in the `ng_module` rule to flatten the types into
a single file. To fix this, we need to update `api-extractor`, but this
unveils the issue with TS API guardian because the most recent version
of api-extractor uses alias exports to avoid potential conflicts
with globals available through the TypeScript default libraries (e.g.
`dom.d.ts`).

PR Close #42688
2021-06-30 11:43:48 -07:00
..
api-golden feat(dev-infra): introduce shared tool for validating API signature (#42688) 2021-06-30 11:43:48 -07:00
browsers refactor(dev-infra): move shared browser bazel setup into dedicated bazel folder (#42268) 2021-06-03 10:37:41 -07:00
remote-execution refactor(dev-infra): switch away from deprecated platform execution properties (#41941) 2021-05-04 21:09:30 -07:00
BUILD.bazel feat(dev-infra): introduce shared tool for validating API signature (#42688) 2021-06-30 11:43:48 -07:00
expand_template.bzl refactor(dev-infra): ng_rollup_bundle rule should leverage `@bazel/rollup` (#37623) 2020-06-22 10:55:28 -07:00