docs: mention MDC migration requirement for legacy Material users#69195
docs: mention MDC migration requirement for legacy Material users#69195akshaywadatkar wants to merge 1 commit into
Conversation
|
Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). View this failed invocation of the CLA check for more information. For the most up to date status, view the checks section at the bottom of the pull request. |
| action: | ||
| 'Run `ng update @angular/material@17`. If your application still uses legacy Angular Material components (deprecated in v15 and removed in v17), run `ng generate @angular/material:mdc-migration` before upgrading to Material v17.', |
There was a problem hiding this comment.
Maybe we could link the v17 MDC migration guide on the note, so users have a path to the full migration steps? Since the note is about upgrading to Material v17, a version-pinned link feels like the right target:
| action: | |
| 'Run `ng update @angular/material@17`. If your application still uses legacy Angular Material components (deprecated in v15 and removed in v17), run `ng generate @angular/material:mdc-migration` before upgrading to Material v17.', | |
| action: | |
| 'Run `ng update @angular/material@17`. If your application still uses legacy Angular Material components (deprecated in v15 and removed in v17), run `ng generate @angular/material:mdc-migration` before upgrading to Material v17. [Read more](https://v17.material.angular.dev/guide/mdc-migration)', |
Also, the existing link on line 1830 looks dead now. It just redirects to the /guides list instead of the actual page. Could be worth fixing, but let's what the caretaker suggests.
PR Checklist
PR Type
What is the current behavior?
The Angular Update Guide currently instructs users to run:
ng update @angular/material@17
However, it does not mention that applications still using legacy Angular Material components may fail to upgrade because legacy components were deprecated in v15 and removed in v17.
Issue Number: N/A
What is the new behavior?
Adds a note to the Angular Update Guide indicating that applications still using legacy Angular Material components should run:
ng generate @angular/material:mdc-migration
before upgrading to Angular Material v17.
This provides additional guidance for users upgrading applications that have not yet migrated to MDC-based components.
Does this PR introduce a breaking change?
Other information
Legacy Angular Material components were deprecated in v15 and removed in v17. This documentation update helps users understand a common upgrade failure scenario and points them to the existing MDC migration path.