-
-
Notifications
You must be signed in to change notification settings - Fork 7.6k
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
Add a --panicOnWarning flag #9357
Comments
bep
changed the title
Add a --panicOnWarning and --panicOnError flag
Add a --panicOnWarning flag
Jan 6, 2022
bep
added a commit
to bep/hugo
that referenced
this issue
Jan 6, 2022
Fixes gohugoio#9357 Fixes gohugoio#9359
bep
added a commit
to bep/hugo
that referenced
this issue
Jan 6, 2022
Fixes gohugoio#9357 Fixes gohugoio#9359
Perhaps intentional but this flag does not panic on hugo --panicOnWarning
Start building sites …
hugo v0.92.0-B3549403+extended linux/amd64 BuildDate=2022-01-12T08:23:18Z VendorInfo=gohugoio
WARN 2022/01/12 23:07:10 .File.TranslationBaseName on zero object. Wrap it in if or with: {{ with .File }}{{ .TranslationBaseName }}{{ end }} |
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. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
This issue is especially targeted at deprecation warnings. These textual references without a file/template context (filename, line number) is sometimes very hard to debug. It would be much nicer if I could do
hugo server --panicOnWarning
and just iterate until the warnings go away.We should also print that flag as part of the deprecation message.
/cc @jmooring
The text was updated successfully, but these errors were encountered: