-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
Add no-unescaped-entities to recommended configuration #841
Milestone
Comments
@ljharb I'm curious what the downsides are to not escaping |
@rauchg The rule documentation should explain it; basically, it's highly likely there's a bug. Separately, it shouldn't impact "writing stuff" at all, since straight quotes are typographically incorrect, and you don't need to escape curly quotes. |
This was referenced Sep 22, 2018
This was referenced Oct 25, 2018
1 task
1 task
1 task
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This rule was added by #681 and I think it should be added to the recommended configuration for the next major version bump.
The text was updated successfully, but these errors were encountered: