Skip to content

Conversation

@Zxilly
Copy link
Contributor

@Zxilly Zxilly commented Jun 19, 2024

@ldez ldez added the area: output Related to issue output label Jun 19, 2024
@ldez
Copy link
Member

ldez commented Jun 19, 2024

There is no severity convention inside golangci-lint but you can override or define your own inside the severity section.

https://golangci-lint.run/usage/configuration/#severity-configuration

@ldez ldez self-requested a review June 19, 2024 20:02
@ldez ldez added this to the next milestone Jun 19, 2024
@Zxilly
Copy link
Contributor Author

Zxilly commented Jun 19, 2024

I'm not familiar with the golangci lint codebase, but I was wondering if an e2e test exists? Maybe we can add to these tests for sarif and we can validate the output json file with a json schema.

@ldez
Copy link
Member

ldez commented Jun 19, 2024

we don't need e2e to validate the output, and to be honest, I was thinking of adding a test about that.
But those tests will not be more useful than the current tests.

@ldez ldez changed the title fix: sarif level property should be enum fix: sanitize level property for SARIF Jun 19, 2024
@ldez ldez added the bug Something isn't working label Jun 19, 2024
Copy link
Member

@ldez ldez left a comment

Choose a reason for hiding this comment

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

LGTM

@ldez ldez merged commit 304e22a into golangci:master Jun 19, 2024
@ldez ldez modified the milestones: next, v1.60 Aug 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area: output Related to issue output bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants