This repository has been archived by the owner on Dec 15, 2022. It is now read-only.
Tokenize HTML as HTML without beautification #64
Merged
Conversation
This file contains 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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Requirements
Description of the Change
The first commit removes the
js-beautifydependency. All our HTML can already be considered "beautified". I did a manual visual check and cannot find any differences between the raw and beautified HTML output. The second commit tokenizes HTML as HTML instead of...XML?Alternate Designs
None.
Benefits
More accurate highlighting through Highlights, as well as one less dependency to install and require.
Possible Drawbacks
Perhaps js-beautify was doing something important.
Applicable Issues
None.