Skip to content
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.

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

Investigate usage of MatLegacy components and modules #18

Closed
zembrodt opened this issue Feb 8, 2024 · 0 comments
Closed

Investigate usage of MatLegacy components and modules #18

zembrodt opened this issue Feb 8, 2024 · 0 comments
Assignees
Labels
bug Something isn't working

Comments

@zembrodt
Copy link
Owner

zembrodt commented Feb 8, 2024

The upgrade to Angular Material 15 causes several components and modules to be named "MatLegacy".

MatLegacy components are no longer supported in Angular Material 17:

Cannot update to Angular Material v17 because the project is using the legacy Material components
that have been deleted. While Angular Material v16 is compatible with Angular v17, it is recommended
to switch away from the legacy components as soon as possible because they no longer receive bug fixes,
accessibility improvements and new features.

Read more about migrating away from legacy components: https://material.angular.io/guide/mdc-migration
@zembrodt zembrodt added the bug Something isn't working label Feb 8, 2024
@zembrodt zembrodt self-assigned this Feb 8, 2024
zembrodt added a commit that referenced this issue Feb 8, 2024
@zembrodt zembrodt closed this as completed Feb 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant