-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Remove "matches" object from schema #15781
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
r- here until webhintio/hint#5126 is solved on the webhintio side.
This pull request has merge conflicts that must be resolved before we can merge this. |
This pull request has merge conflicts that must be resolved before we can merge this. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, but
edit: And there was the concern about webhintio/hint#5126.
This pull request has merge conflicts that must be resolved before we can merge this. |
This pull request has merge conflicts that must be resolved before we can merge this. |
This pull request has merge conflicts that must be resolved before we can merge this. |
@queengooborg @Elchi3 @caugner, we've finished preparing for this removal on the webhint side. Feel free to move forward and thanks for giving us the heads-up + some time to adapt before this went in! 😊 |
Thanks @antross for the notice! |
This PR removes the
matches
object from the schema. The feature is hardly used anywhere other than a few CSS properties and has not been maintained. On top of it, the linter to verifymatches
regexes was never actually integrated into the linter run.Note: in regards to the
transform
CSS property, I'm thinking that we should separate the keywords out, but I'm not fully certain on that.Fixes #8945.