-
-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Better error message #1771
Comments
slug not foundHexo fails silently upon this: Test all tag plugins and check how they handle space |
|
Missing theme |
Better trace of invalid tagThe erroneous tag/syntax causing Nunjunk/Swig error are not easy to read. The line and column refer to intermediate HTML generated from MD. unexpected token
unknown block tag
unexpected end of file
expected end of comment, got end of file
|
Thank you for looking into these. |
The error message that hexo s or g print is very bad. It doesn't mention which file, row and columns that cause generating failure. So every time I have to spend long time finding what error is |
Stack trace colorCurrently the stack track is logged in grey, which is hard to read
|
did this ever get merged? Seeing an unknown tag error, and while I can grep for the tag, a readable error message rather than a stack trace that listed the source file would be 💯 |
ping @tommy351, please merge the PR for hexo-log first. |
Both changes are merged, thank you. |
It helps the user identify and fix errors if we
Do comment if you found some area that needs improving.
EDIT I have a WIP branch here:
https://github.com/leesei/hexo/commits/better-error-message
To use this branch:
The text was updated successfully, but these errors were encountered: