X Tutup
The Wayback Machine - https://web.archive.org/web/20201214110008/https://github.com/validator/validator/issues/1044
Skip to content

/ validator

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

Jump to bottom

Enable filtering also on the file path prefix #1044

Open
Mi-La opened this issue Nov 23, 2020 · 1 comment
Open

Enable filtering also on the file path prefix #1044

Mi-La opened this issue Nov 23, 2020 · 1 comment

Comments

@Mi-La
Copy link

@Mi-La Mi-La commented Nov 23, 2020

Currently the filter pattern matches only the error message. It would be handy to match also in the path part to enable filtering based on the filename or even the specific line number.

/home/test/somepath/SomeFile.html:230.42-230.50: error: Element “invalid” not allowed as child of element “p” in this context. (Suppressing further errors from this subtree.)

It would nice to be allowed to use filter patterns like: .*SomeFile.html.* or even .*SomeFile.html:230.*.
@Mi-La
Copy link
Author

@Mi-La Mi-La commented Nov 23, 2020

Note that usually you get multiple error messages caused by a single error, e.g.:

"file:/home/test/invalid.html":230.42-230.50: error: Element “invalid” not allowed as child of element “p” in this context. (Suppressing further errors from this subtree.)
"file:/home/test/invalid.html":230.82-230.85: error: End tag “p” seen, but there were open elements.
"file:/home/test/invalid.html":230.42-230.50: error: Unclosed element “invalid”

And it's not much comfortable to filter out each single message.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant
@Mi-La
You can’t perform that action at this time.
X Tutup