[META] Make it possible to inspect twig variables and get information about objects and render arrays

Excellent idea! I would be happy to work on this when the time is right.

Here are some ideas:

@dealancer just presented me his sandbox for auto-completion of entity metadata things. That got me the idea. We _can_ wrap entities within a MetaDataWrapper Container and such could have easy: node.title, node.body.value, etc. And even {% getInfo(node) %}, which could give the properties based on the meta-data. As we are controlling access to all variables already anyway, we can easily wrap objects of type "entity" with the wrapper. That could even allow code-completion via IDE :-). - Fabianx

Here are some links for later reference:

http://drupal.org/node/1021556
http://drupal.org/sandbox/vackar/1806252

It is active!

Having read this and #1805526: {{ _self }} in the frontend => How do I dump or debug things? what is actually desired in the end?

On the other thread the following is mentioned:

<pre style="overflow: scroll; height: 300px">
{{ dump(_self) }}
</pre>

or just {{ dump() }} for the whole context.

Are you wanting something more like the Krumo / kpr() command which does the collapsed drill-down data?

Yes, wanted some token like browser to drill down into variables, but will do so in contrib probably.

Moving to core and making it meta.

Update issue

Tagging.

There is a similar discussion about dumping out variables going on here https://drupal.org/node/1804998 (Add LadyBug from Symphony to Core to allow debugging variables within templates)

Add related issue

Adding a relation to #2114563: Remove TwigReference with the help of 'without' filter replacing 'show'/'hide' functions. as it currently prevents dump() from doing anything useful along with other things.

I think this should be explored in contrib first. We do have some fairly nice things like the Kint module that is part of the Devel module in D8 contrib and I'm excited for other possibilities!

We can add experimental support, or full support, for this, in a minor release.

Write a proof-of-concept approach

I just added an integration for Symfony VarDumper component to Twig tweak module. We may consider this as a proof of concept.

The {{ drupal_dump() }} function in Twig Tweak module isn't a "proof of concept" for this issue (read issue this issue and its summary).

It's just a wrapper around {{ dump() }} (which we already have). Thus, this module is actually duplicating (and confusing) existing functionality.

This issue is, specifically, about providing better information about variables; not just "dumping them". In particular, and in regard to render arrays, the #type and #theme hook used.

This also doesn't change the state of #11, so setting back to postponed.

edit: updated link to correct comment number for why this issue is postponed.

I agree the issue is not just about dumping.

duplicating (and confusing) existing functionality

Unfortunately existing functionality is not quite useful because it relies on pure PHP var_dump function.

so setting back to postponed

Can you explain why? The issue is targeted against 8.4. What are we waiting for?

Thank you for creating this issue to improve Drupal.

We are working to decide if this task is still relevant to a currently supported version of Drupal. There hasn't been any discussion here for over 8 years which suggests that this has either been implemented or is no longer relevant. Your thoughts on this will allow a decision to be made.

Since we need more information to move forward with this issue, the status is now Postponed (maintainer needs more info). If we don't receive additional information to help with the issue, it may be closed after three months.

Thanks!

For this one the child issues are all closed so wonder what's next?

I think this has been resolved in #3306864: Integrate Twig with Symfony VarDumper for improved debugging experience.