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

Problem matcher severity handles "Note" and "Hint" as errors #452

Closed
Wosi opened this issue Nov 22, 2015 · 3 comments
Closed

Problem matcher severity handles "Note" and "Hint" as errors #452

Wosi opened this issue Nov 22, 2015 · 3 comments
Assignees
Labels
feature-request Request for new features or functionality tasks Task system issues
Milestone

Comments

@Wosi
Copy link

Wosi commented Nov 22, 2015

I'm using a problem matcher that handles compiler outputs. The messages can have the severities Note, Hint, Warning, Error and Fatal.
The last three are displayed correctly but the first two severities are displayed as errors too. Can I define a mapping for serverities anywhere?

@dbaeumer
Copy link
Member

A problemMatcher has a severity property. The property will be used as a default value when no severity can be located in the message itself. In you case:

            "problemMatcher": {
                ...
                "severity": "warning"
                ...
            }

Should do the trick.

@Wosi
Copy link
Author

Wosi commented Nov 23, 2015

Thanks, but that's not a solution at all.
The severities Note and Warning are now handled correctly but Fatal has now the new default severity too.
Is there a way to declare my own mapping for severities?

@dbaeumer
Copy link
Member

@Wosi currently not. I reopen the issue.

@dbaeumer dbaeumer reopened this Nov 30, 2015
@dbaeumer dbaeumer added feature-request Request for new features or functionality tasks Task system issues labels Nov 30, 2015
@egamma egamma modified the milestone: Backlog Dec 10, 2015
@dbaeumer dbaeumer modified the milestones: May 2017, Backlog May 3, 2017
@vscodebot vscodebot bot locked and limited conversation to collaborators Nov 18, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
feature-request Request for new features or functionality tasks Task system issues
Projects
None yet
Development

No branches or pull requests

3 participants