Add command to dump template variables

[bep]

See http://discuss.gohugo.io/t/the-never-ending-confusion-over-variables/804/10

• Not sure on what level this should be performed, site, page?
• Reflection should be able to read out the exported fields and funcs in a template context

[mdhender]

I thought that we could write a for loop in the template to iterate through all the values in . and dump the values as needed. I added two functions in PR #1026 to help:

1. "inspect" is similar to printf "%#v".
2. "typeOf" returns the type of a variable or value.

[mdhender]

Future thoughts - given how fast Hugo is, would it be possible to have a template hiding on the back end that did a pretty print of the current environment and passed that through CSS to float a window that displayed the results in a navigable hierarchy?

[bep]

Yes - that's a good idea ... but since the current context is per page/node, it should be some kind of DebugWrapper around each html file.

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.