-
-
Notifications
You must be signed in to change notification settings - Fork 9.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
Feature proposal: report syntax errors in the web page #6248
Labels
Comments
This comment has been minimized.
This comment has been minimized.
This would be pretty cool, so long as it only happened in the dev environment. 👍 |
This comment has been minimized.
This comment has been minimized.
now that we have core support for livereload, in theory we could achieve this by having a websocket load an |
This comment has been minimized.
This comment has been minimized.
I want to try to implement this feature, but I'm completely new to jekyll. Can someone give me some advices? :) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Problem: Frequently while running
jekyll serve --watch
and editing a file, I'll introduce a syntax error and not notice, because I'm just looking back and forth between the editor and the browser, and don't have the terminal in my field of view.One solution, that requires modifying user behavior, is for the user to have all three panes up and scan them all.
Another is to implement a “syntax error overlay”. The create-react-app project reports syntax errors in the web page, as well as on the console. This PR begins with a screenshot that illustrates this.
This would be a nice feature for Jekyll too. It could look something like this:
(This particular screenshot is from a Jekyll clone. That's why the error message is different from what Jekyll would report. I've found it helpful there. If anyone wants to take this on, you are of course welcome to use the clone's CSS and Liquid template.)
The text was updated successfully, but these errors were encountered: