-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Display template path of current page in dev mode #18717
Conversation
Maybe we can show all rendered template file paths in TRACE level. There are a lot of embedded templates, they can not be found by this PR's mechanism. |
This will display the entry template path. Once you can open that file, you can find the embedded templates. I don't think it's meaningful to display them in trace log. You can always find them in the entry template as soon as you want. If we really want to know that, we can reject some js or css code around the embbeded template to add some box lines and title in the pages to indicate which area is from which template. |
Would suggest |
Or maybe: Either is fine to me. |
9943555
to
640f64e
Compare
@wxiaoguang I changed the name and for the position I followed @silverwind's advice because templatename maybe blank. and |
Co-authored-by: silverwind <me@silverwind.io>
* giteaofficial/main: Send mail to issue/pr assignee/reviewer also when OnMention is set (go-gitea#18707) Reduce CI go module downloads, add make targets (go-gitea#18708) Add number in queue status to monitor page (go-gitea#18712) Fix source code line highlighting (go-gitea#18729) Fix forked repositories missed tags (go-gitea#18719) [skip ci] Updated translations via Crowdin Fix release typo (go-gitea#18728) Display template path of current page in dev mode (go-gitea#18717) Separate the details links of commit-statuses in headers (go-gitea#18661) Add LDAP group sync to Teams, fixes go-gitea#1395 (go-gitea#16299) Change git.cmd to RunWithContext (go-gitea#18693)
* Display template path of current page in dev mode * improve code * Update templates/base/footer_content.tmpl Co-authored-by: silverwind <me@silverwind.io> Co-authored-by: wxiaoguang <wxiaoguang@gmail.com> Co-authored-by: silverwind <me@silverwind.io>
For developing, when a page has problem, we have to investigate which template is the page. Now the template path will be displayed in the footer nearby template load time if it's develop mode.