Skip to content
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

more friendly message for no-unescaped-entities #2016

Merged
merged 1 commit into from Jan 21, 2019

Conversation

stevemao
Copy link
Contributor

No description provided.

@stevemao
Copy link
Contributor Author

BTW, why is & not in the default?

@stevemao
Copy link
Contributor Author

@ljharb Do you also want to change the option to be array of

{
  char,
  alternatives,
}

This would become a breaking change (change from array of strings)?

@ljharb
Copy link
Member

ljharb commented Dec 15, 2018

I definitely want to avoid a breaking change.

@stevemao stevemao force-pushed the feature/improve-escape-error branch 2 times, most recently from 97edfb0 to 9dde951 Compare December 16, 2018 00:34
```

Where `char` is a special character and `alternatives` is the correct escapes.
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also added docs

@ljharb
Copy link
Member

ljharb commented Jan 3, 2019

(I'm going to hold off merging it for awhile while the 7.12 release settles down)

Copy link
Collaborator

@EvHaus EvHaus left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

None yet

3 participants