docs: Mention Bazel builder and schematics in Deprecations section (#37190)
This commit adds Bazel builder and schematics to the global list of deprecations in Angular. A link to the migration doc is added. PR Close #37190
This commit is contained in:
parent
08ff8aa055
commit
bd7393fc68
|
@ -35,6 +35,7 @@ v9 - v12
|
|||
|
||||
| Area | API or Feature | May be removed in |
|
||||
| ----------------------------- | --------------------------------------------------------------------------- | ----------------- |
|
||||
| `@angular/bazel` | [`Bazel builder and schematics`](#bazelbuilder) | v10 |
|
||||
| `@angular/common` | [`ReflectiveInjector`](#reflectiveinjector) | <!--v8--> v11 |
|
||||
| `@angular/common` | [`CurrencyPipe` - `DEFAULT_CURRENCY_CODE`](api/common/CurrencyPipe#currency-code-deprecation) | <!--v9--> v11 |
|
||||
| `@angular/core` | [`CollectionChangeRecord`](#core) | <!--v7--> v11 |
|
||||
|
@ -160,7 +161,11 @@ Tip: In the [API reference section](api) of this doc site, deprecated APIs are i
|
|||
|
||||
This section lists all of the currently-deprecated features, which includes template syntax, configuration options, and any other deprecations not listed in the [Deprecated APIs](#deprecated-apis) section above. It also includes deprecated API usage scenarios or API combinations, to augment the information above.
|
||||
|
||||
{@a bazelbuilder}
|
||||
### Bazel builder and schematics
|
||||
|
||||
Bazel builder and schematics were introduced in Angular Labs to let users try out Bazel without having to manage Bazel version and BUILD files.
|
||||
This feature has been deprecated. For more information, please refer to the [migration doc](https://github.com/angular/angular/blob/master/packages/bazel/src/schematics/README.md).
|
||||
|
||||
{@a wtf}
|
||||
### Web Tracing Framework integration
|
||||
|
|
|
@ -15,8 +15,6 @@ In the beginning of this project, we thought it would make Bazel easier for
|
|||
users to adopt if we abstracted the BUILD files management and tooling
|
||||
orchestration within Angular CLI. However, we have come to realize that such
|
||||
abstraction does not encourage users to use Bazel to its full potential.
|
||||
There is currently a [prototype](https://github.com/bazelbuild/rules_nodejs/tree/master/examples/angular_bazel_architect)
|
||||
that showcases how multiple architects within CLI could be orchestrated by Bazel.
|
||||
|
||||
There are a few other reasons for this deprecation:
|
||||
|
||||
|
@ -24,7 +22,9 @@ There are a few other reasons for this deprecation:
|
|||
2. The introduction of the Angular Ivy compiler enables new ways to use Bazel
|
||||
in a faster and more efficient manner (see below).
|
||||
3. Feature parity with Webpack-based Angular CLI is difficult to achieve without
|
||||
trade-offs that would not be acceptable for many Angular users.
|
||||
trade-offs that would not be acceptable for many Angular users.
|
||||
There is currently a [prototype](https://github.com/bazelbuild/rules_nodejs/tree/master/examples/angular_bazel_architect)
|
||||
that showcases how multiple architects within CLI could be orchestrated by Bazel.
|
||||
|
||||
## Migrate from `@angular/bazel`
|
||||
|
||||
|
|
Loading…
Reference in New Issue