Prettyhtml. Fix #561. Fix #491 #912
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
|
Hi @octref I just released an overwhelmed version of prettyhtml. Please upgrade to the latest version. This includes a new parser which is less strict and much easier to maintain. The issues above should be already gone. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
@StarpTech I ran it through a few real-world examples. Overall looking pretty good!
If you can handle Prettyhtml/prettyhtml#29 and Prettyhtml/prettyhtml#28 I believe it's good to go.
As for the options, I would suggest
usePrettier->formatEmbeddedContent. It's not a deal breaker for me but hope it can be more explicit.Todos for myself: