fix(material/sort): fix undefined object access

[swftvsn]

This commit fixes hard crash that results from accessing undefined object's property.

[crisbeto]

The code looks good, but you have to run yarn approve-api sort and commit the changed file.

[swftvsn]

The code looks good, but you have to run yarn approve-api sort and commit the changed file.

Unfortunately I'm doing the edits from the GitHub web-interface, so it'll be some weeks (considering my workload atm) before I'm able to setup the whole dev environment for components.

[chunghha]

Instead of waiting, can we get this PR merged for a release as this is a production bug to who use current v11 version in their production?

[aailyin]

Instead of waiting, can we get this PR merged for a release as this is a production bug to who use current v11 version in their production?

The same problem.
@swftvsn When are going to release this fix?

[swftvsn]

Instead of waiting, can we get this PR merged for a release as this is a production bug to who use current v11 version in their production?

The same problem.
@swftvsn When are going to release this fix?

I have no relation to angular and unfortunately I'm drowning in work. My superiors have so far prioritised other work and they are ok to be on the version that still works for some months. TL:DR; If you need this fixed please open a new PR to address it which corrects the issues @crisbeto described above. That or beg that someone on the team takes it.

[crisbeto]

@swftvsn I can pick it up and make sure that the CI passes.

[chunghha]

Opened #22634

Thanks @swftvsn for the fix.

[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.}