Giulia Stocco
Giulia Stocco
This will be fixed with #361 which transitions the VS Code extension to use the same .NET backend.
The update to .NET 5 made the .NET compiler realize that blazor was referencing the cli, which is not allowed as it is a non-self-contained executable and no longer allows...
Blazor interface is retired with 0.7. It may be brought back later in a rewritten state.
From some preliminary analysis of the difference where Rules have diverged DevSkim has some additional fields: does not apply fix its It likely makes sense to extend the AI Rule...
Work to make the api format work and support those missing devskim features was added in: https://github.com/microsoft/ApplicationInspector/pull/471 and is available in AI 1.5.17 and later.
Completed with 0.7.
Is this for the VS Code or Visual Studio extension? > configuring a rule differently per language would be more difficult or tedious. See the DotNet and Roslyn rules for...
It doesn't look like they have a C# API on their roadmap. https://github.com/returntocorp/semgrep -------- Original Message -------- On May 9, 2020, 12:14 PM, Michael Scovetta wrote: > Looks like it...
~Depends on https://github.com/returntocorp/semgrep/issues/1309~
@daalcant please provide an update when this is closed.