You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Right now, there is no good way to tell which dll has which analyzers.
It is hard to tell what codes the analyzer can produce and what the name is in case you potentially want to exclude it.
Describe the solution you'd like
I'm thinking some sub-command could be interesting. Something like dotnet fsharp-analyzers inspect MyAnalyzer.dll.
This prints a table overview of all the analyzers found in the tool.
Describe alternatives you've considered
Maybe adding the name to the sarif output might also work.
Although you need to trigger a message before seeing it, which isn't always super obvious.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Right now, there is no good way to tell which dll has which analyzers.
It is hard to tell what codes the analyzer can produce and what the name is in case you potentially want to exclude it.
Describe the solution you'd like
I'm thinking some sub-command could be interesting. Something like
dotnet fsharp-analyzers inspect MyAnalyzer.dll
.This prints a table overview of all the analyzers found in the tool.
Describe alternatives you've considered
Maybe adding the name to the sarif output might also work.
Although you need to trigger a message before seeing it, which isn't always super obvious.
The text was updated successfully, but these errors were encountered: