-
-
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
Get file context in "config parse failed" errors #5325
Comments
bep
added a commit
to bep/hugo
that referenced
this issue
Oct 16, 2018
The main item in this commit is showing of errors with a file context when running `hugo server`. This can be turned off: `hugo server --disableBrowserError` (can also be set in `config.toml`). But to get there, the error handling in Hugo needed a revision. There are some items left TODO for commits soon to follow, most notable errors in content and config files. Fixes gohugoio#5284 Fixes gohugoio#5290 See gohugoio#5325 See gohugoio#5324
bep
added a commit
to bep/hugo
that referenced
this issue
Oct 16, 2018
The main item in this commit is showing of errors with a file context when running `hugo server`. This can be turned off: `hugo server --disableBrowserError` (can also be set in `config.toml`). But to get there, the error handling in Hugo needed a revision. There are some items left TODO for commits soon to follow, most notable errors in content and config files. Fixes gohugoio#5284 Fixes gohugoio#5290 See gohugoio#5325 See gohugoio#5324
bep
added a commit
to bep/hugo
that referenced
this issue
Oct 16, 2018
The main item in this commit is showing of errors with a file context when running `hugo server`. This can be turned off: `hugo server --disableBrowserError` (can also be set in `config.toml`). But to get there, the error handling in Hugo needed a revision. There are some items left TODO for commits soon to follow, most notable errors in content and config files. Fixes gohugoio#5284 Fixes gohugoio#5290 See gohugoio#5325 See gohugoio#5324
bep
added a commit
to bep/hugo
that referenced
this issue
Oct 16, 2018
The main item in this commit is showing of errors with a file context when running `hugo server`. This can be turned off: `hugo server --disableBrowserError` (can also be set in `config.toml`). But to get there, the error handling in Hugo needed a revision. There are some items left TODO for commits soon to follow, most notable errors in content and config files. Fixes gohugoio#5284 Fixes gohugoio#5290 See gohugoio#5325 See gohugoio#5324
bep
added a commit
to bep/hugo
that referenced
this issue
Oct 16, 2018
The main item in this commit is showing of errors with a file context when running `hugo server`. This can be turned off: `hugo server --disableBrowserError` (can also be set in `config.toml`). But to get there, the error handling in Hugo needed a revision. There are some items left TODO for commits soon to follow, most notable errors in content and config files. Fixes gohugoio#5284 Fixes gohugoio#5290 See gohugoio#5325 See gohugoio#5324
bep
added a commit
to bep/hugo
that referenced
this issue
Oct 16, 2018
The main item in this commit is showing of errors with a file context when running `hugo server`. This can be turned off: `hugo server --disableBrowserError` (can also be set in `config.toml`). But to get there, the error handling in Hugo needed a revision. There are some items left TODO for commits soon to follow, most notable errors in content and config files. Fixes gohugoio#5284 Fixes gohugoio#5290 See gohugoio#5325 See gohugoio#5324
bep
added a commit
to bep/hugo
that referenced
this issue
Oct 22, 2018
bep
added a commit
to bep/hugo
that referenced
this issue
Oct 22, 2018
bep
added a commit
to bep/hugo
that referenced
this issue
Oct 22, 2018
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.
Related to #5284 -- this config loading is a little bit hidden inside Viper.
The text was updated successfully, but these errors were encountered: