Add Herb LSP extension to ruby devcontainer feature
#102
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
After talking to @rafaelfranca we agreed to adding the Herb LSP VS Code Extension to the devcontainer setup so more people can start using it in their day-to-day work.
The Herb Visual Studio Code Extension is specifically designed to work with HTML+ERB files and is built on top of the HTML-aware ERB parser, called Herb.
The Herb Language Server currently offers the functionality to catch HTML/Ruby syntax errors in HTML+ERB files (using Prism), run the Herb Linter to catch common issues/enforce best practices, and auto-format HTML+ERB documents on-save using the Herb Formatter. There's a lot more to come.
To follow along, to report issues, or to share feature ideas you can open an issue on the Herb here on GitHub. Thank you!