From ed110a05f05a6875c7dcd489bea57d8fcdfff34a Mon Sep 17 00:00:00 2001 From: Andrew Scott Date: Tue, 28 Feb 2023 09:21:01 -0800 Subject: [PATCH] docs: remove deprecation notes for removed APIs (#49239) This commit removes the deprecation notes from the deprecations guide for APIs that have been removed. PR Close #49239 --- aio/content/guide/deprecations.md | 13 ------------- aio/content/guide/update-to-version-14.md | 4 ++-- 2 files changed, 2 insertions(+), 15 deletions(-) diff --git a/aio/content/guide/deprecations.md b/aio/content/guide/deprecations.md index de199704afb..d3ce44092da 100644 --- a/aio/content/guide/deprecations.md +++ b/aio/content/guide/deprecations.md @@ -98,9 +98,6 @@ v16 - v19 | `@angular/platform-browser-dynamic` | [`JitCompilerFactory`](#platform-browser-dynamic) | v13 | v16 | | `@angular/platform-browser-dynamic` | [`RESOURCE_CACHE_PROVIDER`](#platform-browser-dynamic) | v13 | v16 | | `@angular/platform-server` | [`ServerTransferStateModule`](#platform-server) | v14 | v16 | -| `@angular/router` | [`relativeLinkResolution`](#relativeLinkResolution) | v14 | v16 | -| `@angular/router` | [`resolver` argument in `RouterOutletContract.activateWith`](#router) | v14 | v16 | -| `@angular/router` | [`resolver` field of the `OutletContext` class](#router) | v14 | v16 | | `@angular/service-worker` | [`SwUpdate#activated`](api/service-worker/SwUpdate#activated) | v13 | v16 | | `@angular/service-worker` | [`SwUpdate#available`](api/service-worker/SwUpdate#available) | v13 | v16 | @@ -194,8 +191,6 @@ In the [API reference section](api) of this site, deprecated APIs are indicated | API | Replacement | Deprecation announced | Details | |:--- |:--- |:--- |:--- | -| [`resolver` argument in `RouterOutletContract.activateWith`](api/router/RouterOutletContract#activatewith) | No replacement needed | v14 | Component factories are not required to create an instance of a component dynamically. Passing a factory resolver via `resolver` argument is no longer needed. | -| [`resolver` field of the `OutletContext` class](api/router/OutletContext#resolver) | No replacement needed | v14 | Component factories are not required to create an instance of a component dynamically. Passing a factory resolver via `resolver` class field is no longer needed. | | [`RouterLinkWithHref` directive](api/router/RouterLinkWithHref) | Use `RouterLink` instead. | v15 | The `RouterLinkWithHref` directive code was merged into `RouterLink`. Now the `RouterLink` directive can be used for all elements that have `routerLink` attribute. | | [`provideRoutes` function](api/router/provideRoutes) | Use `ROUTES` `InjectionToken` instead. | v15 | The `provideRoutes` helper function is minimally useful and can be unintentionally used instead of `provideRouter` due to similar spelling. | | [`setupTestingRouter` function](api/router/testing/setupTestingRouter) | Use `provideRouter` or `RouterTestingModule` instead. | v15.1 | The `setupTestingRouter` function is not necessary. The `Router` is initialized based on the DI configuration in tests as it would be in production. | @@ -465,14 +460,6 @@ matched at all and also prevent loading the children of the `Route`. `CanMatch` goals as `CanLoad` but with the addition of allowing the navigation to match other routes when they reject (such as a wildcard route). There is no need to have both types of guards in the API surface. - - -The `relativeLinkResolution` option is deprecated and being removed. -In version 11, the default behavior was changed to the correct one. -After `relativeLinkResolution` is removed, the correct behavior is always used without an option to use the broken behavior. - -A dev mode warning was added in v14 to warn if a created `UrlTree` relies on the `relativeLinkResolution: 'legacy'` option. - ### `loadChildren` string syntax diff --git a/aio/content/guide/update-to-version-14.md b/aio/content/guide/update-to-version-14.md index 5ee768858c9..6fd945ff2d2 100644 --- a/aio/content/guide/update-to-version-14.md +++ b/aio/content/guide/update-to-version-14.md @@ -65,8 +65,8 @@ For information about the deprecation and removal practices of Angular, see [Ang | [`JitCompilerFactory`](api/platform-browser-dynamic/JitCompilerFactory) | n/a | Ivy JIT mode doesn't require accessing this symbol. See [JIT API changes due to ViewEngine deprecation](guide/deprecations#jit-api-changes) for additional context. | | [`RESOURCE_CACHE_PROVIDER`](api/platform-browser-dynamic/RESOURCE_CACHE_PROVIDER) | n/a | This was previously necessary in some cases to test AOT-compiled components with View Engine, but is no longer since Ivy. | | `relativeLinkResolution` in the Router [`ExtraOptions`](api/router/ExtraOptions) | Switch to the default of `'corrected'` link resolution | This option was introduced to fix a bug with link resolution in a backwards compatible way. Existing apps which still depend on the buggy legacy behavior should switch to the new corrected behavior and stop passing this flag. | -| `resolver` argument in [`RouterOutletContract.activateWith`](api/router/RouterOutletContract#activateWith) | n/a | `ComponentFactory` and `ComponentFactoryResolver` afre deprecated, and passing an argument for a resolver to retrieve a `ComponentFactory` is no longer required. | -| [`OutletContext#resolver](api/router/OutletContext#resolver) | n/a | `ComponentFactory` and `ComponentFactoryResolver` are deprecated, and using a resolver to retrieve a `ComponentFactory` is no longer required. | +| `resolver` argument in [`RouterOutletContract.activateWith`](api/router/RouterOutletContract#activateWith) | n/a | `ComponentFactory` and `ComponentFactoryResolver` are deprecated, and passing an argument for a resolver to retrieve a `ComponentFactory` is no longer required. | +| [`OutletContext#resolver](https://v14.angular.io/api/router/OutletContext#resolver) | n/a | `ComponentFactory` and `ComponentFactoryResolver` are deprecated, and using a resolver to retrieve a `ComponentFactory` is no longer required. | | [`SwUpdate#activated`](api/service-worker/SwUpdate#activated) | Return value of [`SwUpdate#activateUpdate`](api/service-worker/SwUpdate#activateUpdate) | The `activated` property is deprecated. Existing usages can migrate to [`SwUpdate#activateUpdate`](api/service-worker/SwUpdate#activateUpdate). | | [`SwUpdate#available`](api/service-worker/SwUpdate#available) | [`SwUpdate#versionUpdates`](api/service-worker/SwUpdate#versionUpdates) | The behavior of [`SwUpdate#available`](api/service-worker/SwUpdate#available) can be achieved by filtering for the [`VersionReadyEvent`](api/service-worker/VersionReadyEvent) from [`SwUpdate#versionUpdates`](api/service-worker/SwUpdate#versionUpdates)