More robust template path hints (block name, block parents

[apiuser]

Feature request from erikhansen, posted on GitHub May 16, 2014

Currently, the "template path hint" feature displays the template name and block class name.

Fabrizio Branca's Aoe_TemplateHints module extends the native Magento 1.x template path hint functionality to add much more information to the hints including:

• Block name (very useful)
• Parent block names
• Module
• Caching status

Here is a screenshot from his blog post, visualizing what this could look like:

I propose that this functionality be built into Magento 2. If Magento accepts this proposal, I may be willing to build this functionality and then issue a pull request to have it incorporated into Magento 2.

[apiuser]

Comment from alankent, posted on GitHub Feb 02, 2015

I checked internally, only to be reminded that this was already approved above by @tkacheva mid last year. So if someone is willing to work on this (based on AOE code as starting point - thanks Fabrizio!), could interested parties leave a note on this issue to coordinate work between you.

[apiuser]

Comment from ryanstreet, posted on GitHub May 28, 2015

I would be willing to work on this issue. Is it still up for grabs?

[apiuser]

Comment from erikhansen, posted on GitHub Jun 02, 2015

@ryanstreet yes, it is still up for grabs, as far as I know. It would be great if you wanted to work on it.

[apiuser]

Comment from ryanstreet, posted on GitHub Jun 02, 2015

Awesome. I'm on it!

[apiuser]

Comment from piotrekkaminski, posted on GitHub Jun 02, 2015

Great @ryanstreet

[apiuser]

Comment from vpietri, posted on GitHub Jun 30, 2015

Thanks @ryanstreet. Looking forward this great module in Magento 2.

[apiuser]

Comment from ryanstreet, posted on GitHub Jul 01, 2015

Your welcome!

[apiuser]

Comment from JamesAnelay, posted on GitHub Nov 12, 2015

[apiuser]

Comment from erikhansen, posted on GitHub Jan 07, 2016

I don't have time to work on this right now, but just pitched in a $25 bounty.

[apiuser]

Comment from ryanstreet, posted on GitHub Jan 12, 2016

Unless someone can get to it sooner, I have this fix slotted in my schedule for February 16. If someone else can get to it, by all means do so.