-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Document Problem Matcher Commands #198
Conversation
docs/problem-matchers.md
Outdated
"owner": "eslint-compact", | ||
"pattern": [ | ||
{ | ||
// The pattern that provides groups to match against |
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.
comments are not legal JSON
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.
we shouldnt suggest customers use them, if it we switch to a different json parser in the future, it might break.
|
||
The following fields are available for problem matchers: | ||
|
||
``` |
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.
a little bit weird since this isnt valid json
might be interesting to see how vscode docs describe it
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.
They put comments in the json
https://code.visualstudio.com/docs/editor/tasks#_defining-a-problem-matcher
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.
fails in nodejs: JSON.parse('{\n// this is a comment\n"a": "b" }')
not sure we should encourage this, binds us to a particular parser
Rendered
Resolves #56