Don't print "_theme()" in twig_debug output

Hi Cottser,
I suggest to simply removes all references to _theme function because print something like a render array would be confusing (too many variations and data).

Luca

Removal of "_theme" in twig debug output as well as removal of test of "_theme" from testTwigDebugMarkup().

Review patch added to comment #4.

@Geizt thanks for posting a patch though the intent isn't to remove the lines entirely as they provide helpful information. Just avoid referencing the internal call to _theme().

It's a bit fuzzy on what to rename it to, but something along the lines of Rendered theme hook: 'node__foo__bar' maybe?

Note theme() doesn't exist anymore and _theme() is internal only. drupal_render($render_array) will render the variables into the template. The #theme property dictates which hook_theme to call the prepeprocess and render a twig template. Hope that helps some.

Attached is a patch that will hopefully achieve what @joelpittet is after. Lets see what the test bot says.

That works for me, @Cottser will that wording work for you as well?

2201789-remove_theme-twig-7.patch no longer applies.

error: patch failed: core/themes/engines/twig/twig.engine:55
error: core/themes/engines/twig/twig.engine: patch does not apply

Rerolled the patch from #7
+ Replaced the PHP_EOL character with a preg_match /s switch (essentially rewrote the string comparison replacing strpos with preg_match for multi-line matching)

I can see some issues:

- Please, don't use tabs for indentation, just use spaces instead ;)
- You can just call the interdiff "interdiff.txt".
- Don't forget to update the issue status as "Needs review" in order to let the testbot to test it.

Great work! Thanks!!

Following rteijeiro comments (thanks):

+ Removed tab characters
+ Renamed interdiff-2201789-7-12.txt to interdiff.txt

Nice work guys, just an FYI, the interdiff.txt naming you did in #12 is not bad, and can be useful to tell at a glance which patch you were working off (if there is any confusion), but usually there isn't and save your self a few seconds and do what @rteijeiro said. Either way, it's up to you on that one, as long as there is one, I'm happy:)

The way you did it in #12 is how it's recommended in the docs so good work also reading them:) @see https://drupal.org/documentation/git/interdiff

I always like your feedback @joelpittet. Thanks!!

Applied the patch and everything seems to work like a charm. It's a RTBC for me. Great work @stefanos.petrakis!!

I know this is rather petty, but I think it's important that the label should really be capitalized like the line before and after RENDERED THEME HOOK:

I have make the patch and the interdiff capitalizing the "Rendered theme hook" text.

Awesome :) Ty! Setting back to RTBC since that was so minor.

I should really start looking at the entire form before submitting lol

So I assume this is fine, since other people with far more theming experience in their pinky finger than I have in all of me worked on this and marked this RTBC, buuuuttt....

Before:

<!-- THEME DEBUG -->
<!-- CALL: _theme('html') -->
<!-- FILE NAME SUGGESTIONS:
   * html--front.html.twig
   * html--.html.twig
   x html.html.twig
-->
<!-- BEGIN OUTPUT from 'core/modules/system/templates/html.html.twig' -->

After:

<!-- THEME DEBUG -->
<!-- RENDERED THEME HOOK: 'html' -->
<!-- FILE NAME SUGGESTIONS:
   * html--front.html.twig
   * html--.html.twig
   x html.html.twig
-->
<!-- BEGIN OUTPUT from 'core/modules/system/templates/html.html.twig' -->

The "before" thing was a word "call" which is a common verb regarding what happens to PHP functions, and its value is something I can easily look up because "_theme()" is something I can search for on api.drupal.org and find docs, etc.

"Rendered theme hook" though feels extremely jargony to me, and it's not clear what to do with that if I want to find out more information. Is there any other term which would be both a) accurate b) not point people to deprecated nonsense, but c) would be clearer to front-end developers new to Drupal what on earth we're talking about here? Or is this really the best term? Like my "beginner mind" would call this something like "Base template" or something, I dunno.

Don't want to cause a huge bikeshed, but since I know Twiggy people are around and sprinting, thought maybe it was worth kicking this back for a quick round of brainstorming. If this is indeed the best term though, that's fine.

@webchick I agree with your concerns it is a bit jargony. Probably doesn't even need the word "Rendered" because that doesn't give any more information to what is going on.

_theme() still does the rendering of the template, though giving that information could be deterimental as it may indicate people to use that now private function.

drupal_render() is what does the load of the work, but again telling people to use that is also not a great idea because twig calls that automagically when an array is being "printed" to the screen. And calling that early makes a string out of the structured data, effectively flattening it.

So... we need a way of saying that the rendered/flattened string came from a renderable array and most likely a '#theme' => 'boink' triggered rendering the template 'boink.html.twig'.

Suggestions?

Re-rolled. Just the text change. Removed the word "Rendered" because it was superfluous information.

This looks good to me, THEME HOOK is clear on what is doing, RENDERED is not needed at all and adds to the confusion.

It passes the test locally, so I put it to retest

Back to RTBC

Cool, I think this works, and is certainly better than telling them to call something they shouldn't. When I google for "theme hook" I'm taken to https://api.drupal.org/api/drupal/modules%21system%21system.api.php/func..., the Drupal 8 version of that is https://api.drupal.org/api/drupal/core%21modules%21system%21system.api.p... and talks about the concept. It's not as good as the overview at https://api.drupal.org/api/drupal/core%21modules%21system%21theme.api.ph... but we could perhaps add a pointer from hook_theme() to that API page in a separate follow-up to help people out.

Committed and pushed to 8.x. Thanks!