bug(ALL): The feedback you will ignore; css class names inconsistency in new material - post 15 about components HOT 2 OPEN

When the migration tool throws the "no component selected" error, you need to select the components that you want to migrate with the space bar.

from components.

Yeah, that worked - thanks. And only irritated me more.
What is the point of that migration if that only adds basic TODO to fix, and makes some really simple replacement?
Better effect I would achieve applying regex replacement, than running that migration.

Look - what is the point of that, if you replace some main class, and I need to anyway go into, find for the replacement, and make it?

I think I am not alone...
https://www.reddit.com/r/Angular2/comments/zm9w8f/angular_material_on_v15_upgrade_is_a_complete_mess/

What is that guys?
https://material.angular.io/components/tabs/api

come on, some consistency... Not to mention that this boolean attribute is by default, guess what, set to true. What is a breaking behavior compared to the previous version?
But you would say - "HEY, it is just an alias, use the original field name". Yes, I would also say. But it does not work.

Very. Well. Engineered.

In terms of engineering and design, what is that?

Just one example - or multiple on the same screen.

I do not know who approved those changes. Any convention? Good practices? ANY backward compatibility (Yeah, some components did not change class names, nearly at all. Nearly). Maintenance? Predictivity?
What did you do with that framework?
Not to mention I need to migrate, because otherwise I will not be able to update angular in some time.

TIP:

That would be simplified to 0.

That could be also deduplicated...

from components.