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

Use Ionide.Analyzers #2978

Merged
merged 27 commits into from
Nov 15, 2023
Merged

Use Ionide.Analyzers #2978

merged 27 commits into from
Nov 15, 2023

Conversation

nojaf
Copy link
Contributor

@nojaf nojaf commented Nov 8, 2023

@nojaf
Copy link
Contributor Author

nojaf commented Nov 8, 2023

@dawedawe any thoughts why we are not seeing these warnings?

@dawedawe
Copy link
Member

dawedawe commented Nov 8, 2023

@dawedawe any thoughts why we are not seeing these warnings?

They are at least here:
https://github.com/fsprojects/fantomas/security/code-scanning?query=pr%3A2978+tool%3AIonide.Analyzers.Cli+is%3Aopen

To me, it seems a bit like the visual behaviour of GitHub is not really deterministic regarding these things.
Maybe the GitHub bot creates comments only for the first PR that adds the code scanning feature 🤷

@nojaf
Copy link
Contributor Author

nojaf commented Nov 14, 2023

I admit defeat when it comes to AnalyzeFSharpProjectUsingFscArgs, I'll explain in more detail in the SDK repository.

Besides that, this is ready for review.

Copy link
Member

@dawedawe dawedawe left a 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 :)

@nojaf nojaf merged commit a7d8e75 into fsprojects:main Nov 15, 2023
5 checks passed
josh-degraw pushed a commit to josh-degraw/fantomas that referenced this pull request Nov 22, 2023
* 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
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

Successfully merging this pull request may close these issues.

2 participants