docs(readme): Add message in README steering people to parse5 if they need HTML5 compliance#1147
Merged
fb55 merged 3 commits intofb55:masterfrom Apr 23, 2022
Merged
Conversation
… need HTML5 compliance. Fixes fb55#1075
Pull Request Test Coverage Report for Build 2212190919
💛 - Coveralls |
Contributor
Author
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
3 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.
I think this is important to steer people to htmlparser2 or parse5 based on this key difference, especially since this difference is fundamental and permanent. It's important to do this up front to save people the time and effort of finding out the hard way.
Fixes #1075
Happy to reword or make any other changes you want, or drop this and leave it all to you :)