Porting command: dev:class:lookup

[cmuench]

Resolves a grouped class name

[robbieaverill]

With the introduction of plugins, perhaps class rewriting might become almost obselete?

[ktomk]

@robbieaverill Well, I might imagine what you want to say, but if so from that standpoint I would tend to add as well that class rewriting should have been used as much as last resort (and by default: not at all) as much as using interceptors in Magento 2 :).

I'm not yet profound with Magento 2 class rewrites so I can't say if it actually exists as it did in Magento 1. However Magento 2 does have class aliasing within the DI layer and that might come more close to what was the class rewrite in Magento 1. I'd say it's not that bad to have some commands related to that in the magerun2 toolchest. Perhaps dev:class:lookup is a well suited command name for such a functionality.

[robbieaverill]

Hi Tom,

Good point. Preference is still relevant for this command especially with
controllers, and the odd rewrite that persists or is needed for a
particular reason.

R

[Vinai]

Reference https://github.com/dmanners/DavidAndVinai_PreferencesInfoCommand/

[cmuench]

Implemented as dev:di:info command.