-
-
Notifications
You must be signed in to change notification settings - Fork 194
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
Use Ionide.Analyzers #2978
Use Ionide.Analyzers #2978
Conversation
@dawedawe any thoughts why we are not seeing these warnings? |
They are at least here: To me, it seems a bit like the visual behaviour of GitHub is not really deterministic regarding these things. |
b8238bb
to
84aaf37
Compare
I admit defeat when it comes to Besides that, this is ready for review. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Turns out, analyzers can really improve a codebase :)
* Use Ionide.Analyzers * Treat as warnings? * Update Ionide.Analyzers * Bump lock files. * Run both analyzer packages * Try relative paths * Touch file * Delete sarif files * Restore CI build * Use repository root as working directory. * Run both analyzer packages. * Fix Ionide reported problems. * Use AnalyzerFlags * Use FSharp.Analyzers.Build * Revert removal of build-devcontainer. * Add code root * Use AnalyzeFSharpProject * Use array postfix. * Address most analyzer reports * Revert "Address most analyzer reports" This reverts commit d8e93ed. * Update FSharp.Analyzer sdk * Update lock files. * Update packages * Use post fix in signature files. * Use 8.0.100 stable SDK. * Update dev container to 8.0.100
Trying out https://github.com/ionide/ionide-analyzers