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.

Sign up for GitHub

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

[SARIF] Investigate if we handle /errorlog:[file][,version] parameter correctly #6079

Closed

costin-zaharia-sonarsource opened this issue Sep 12, 2022 · 1 comment

Labels

Type: UX

Member

costin-zaharia-sonarsource commented Sep 12, 2022 •

edited

Loading

Scanner4net is not handling this properly. We need to check the behavior in sonar-dotnet too.

Similar with: SonarSource/sonar-scanner-msbuild#1176

costin-zaharia-sonarsource added the Type: Improvement label

Contributor

pavel-mikula-sonarsource commented Sep 12, 2022

There's no handling on sonar-dotnet side AFAICT. It's S4NET responsibility to handle this parameter correctly.

Suppporting Sarif 2.0 or Sarif 2.1 is a different story / MMF (that will not work without support on S4NET side)

pavel-mikula-sonarsource added Type: UX and removed Type: Improvement labels

costin-zaharia-sonarsource closed this as completed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment