Skip to content

build: fix wrong anchors in docs #19375

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
May 15, 2020
Merged

build: fix wrong anchors in docs #19375

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions guides/v9-hammerjs-migration.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -36,7 +36,7 @@ by default in Angular versions 8 and below.
If your application provides a custom [`HAMMER_GESTURE_CONFIG`][1] and also references the
deprecated Angular Material `GestureConfig`, the migration will print a warning about
ambiguous usage. The migration cannot migrate your project automatically and manual changes
are required. Read more [in the dedicated section](#The-migration-reported-ambiguous-usage-What-should-I-do).
are required. Read more [in the dedicated section](#the-migration-reported-ambiguous-usage-what-should-i-do).

### How does the schematic remove HammerJS?

Expand All @@ -62,12 +62,12 @@ import 'hammerjs';

The migration cannot automatically remove HammerJS from tests. Please manually clean up
the test setup and resolve any test issues. Read more in a
[dedicated section for test migration](#How-to-migrate-my-tests).
[dedicated section for test migration](#how-to-migrate-my-tests).

### How do I migrate references to the deprecated `GestureConfig`?

The `GestureConfig` can be consumed in multiple ways. The migration covers the most common cases.
The most common case is that an `NgModule` in your application directly provides `GestureConfig`:
The most common case is that an `NgModule` in your application directly provides `GestureConfig`:

```typescript
import {GestureConfig} from '@angular/material/core';
Expand Down