-
-
Notifications
You must be signed in to change notification settings - Fork 7.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Include location of sources in final output #2609
Comments
I was going to say I didn't think this was possible, but we could modify the templates before they are parsed and add this information. Maybe we could add this whenever we run in watch mode? |
This issue has been automatically marked as stale because it has not been commented on for at least four months. The resources of the Hugo team are limited, and so we are asking for your help. If this is a bug and you can still reproduce this error on the If this is a feature request, and you feel that it is still relevant and valuable, please tell us why. This issue will automatically be closed in four months if no further activity occurs. Thank you for all your contributions. |
Note/Update: This issue is marked as stale, and I may have said something earlier about "opening a thread on the discussion forum". Please don't. If this is a bug and you can still reproduce this error on the latest If this is a feature request, and you feel that it is still relevant and valuable, please tell us why. |
I still think this would be useful to have for debugging. As explained in the documentation, there are several possible locations for sources, like _default, or layouts in the hugo tree, or layouts in the theme tree. The order is well known, but when you're looking at a generated html output file, it helps if you know immediately where to look for the problem instead of going down the list of possibilities. |
I agree. Not the simplest to solve, but we should try. |
When debugging problems, I spend a lot of time figuring out where the template or source is located.
Some template files may be overridden by a copy under /layouts/
Some pages are generated from several partial templates.
It would help a lot if the output (perhaps as a debugging option) contains where the template xxx.html starts.
The text was updated successfully, but these errors were encountered: