bug(migration): Invalid import after migration

[mcalmus]

Is this a regression?

• Yes, this behavior used to work in the previous version

The previous version in which this bug was not present was

No response

Description

Migration from Material 14 to Material 15 left a compile error

Reproduction

Steps to reproduce:

1. Create an Angular/Material 14 project
2. Have MatOptionSelectionChange import in some component
3. Migrate to Angular/Material 15

Expected Behavior

Code compiles

Actual Behavior

Compile error:

'"@angular/material/legacy-core"; has no exported member named 'MatLegacyOptionSelectionChange'. Did you mean 'MatOptionSelectionChange'?

import {MatLegacyOptionSelectionChange as MatOptionSelectionChange } from '@angular/material/legacy-core';

Environment

• Angular: 15.0.0-next.2
• CDK/Material: 15.0.0-next.1
• Browser(s): n/a
• Operating System (e.g. Windows, macOS, Ubuntu): Windows

[json-derulo]

fixed by #25673

[crisbeto]

Closing as fixed.

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}