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

Add inspect sub command #123

Open
nojaf opened this issue Oct 24, 2023 · 0 comments
Open

Add inspect sub command #123

nojaf opened this issue Oct 24, 2023 · 0 comments

Comments

@nojaf
Copy link
Contributor

nojaf commented Oct 24, 2023

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant