FSharp.Analyzers.SDK.Testing
0.42.0
See the version list below for details.
dotnet add package FSharp.Analyzers.SDK.Testing --version 0.42.0
NuGet\Install-Package FSharp.Analyzers.SDK.Testing -Version 0.42.0
<PackageReference Include="FSharp.Analyzers.SDK.Testing" Version="0.42.0" />
<PackageVersion Include="FSharp.Analyzers.SDK.Testing" Version="0.42.0" />
<PackageReference Include="FSharp.Analyzers.SDK.Testing" />
paket add FSharp.Analyzers.SDK.Testing --version 0.42.0
#r "nuget: FSharp.Analyzers.SDK.Testing, 0.42.0"
#:package FSharp.Analyzers.SDK.Testing@0.42.0
#addin nuget:?package=FSharp.Analyzers.SDK.Testing&version=0.42.0
#tool nuget:?package=FSharp.Analyzers.SDK.Testing&version=0.42.0
Ionide FSharp.Analyzers.SDK
Library used for building custom analyzers for FSAC / F# editors.
F# analyzers are live, real-time, project based plugins that enables to diagnose source code and surface custom errors, warnings and code fixes into editor. Read more about analyzers here - https://medium.com/lambda-factory/introducing-f-analyzers-772487889429
How to build
- Install the .NET SDK version specified in
global.json dotnet tool restore- Open and build in your favorite IDE, or use
dotnet build
How to run sample
dotnet build -c Release- Run the console application:
dotnet run --project src\FSharp.Analyzers.Cli\FSharp.Analyzers.Cli.fsproj -- --project ./samples/OptionAnalyzer/OptionAnalyzer.fsproj --analyzers-path ./artifacts/bin/OptionAnalyzer/release --verbosity d
You can also set up a run configuration of FSharp.Analyzers.Cli in your favorite IDE using similar arguments. This also allows you to debug FSharp.Analyzers.Cli.
Using Analyzers
Checkout our Getting Started guide for analyzer users!
Upgrading with an AI agent
This repository ships an agent skill that upgrades the fsharp-analyzers tool and your analyzer packages to a matching set of versions, re-runs the analyzers and reports what is new. Install it globally with:
npx skills add ionide/FSharp.Analyzers.SDK --skill upgrade-fsharp-analyzers -g
Then ask your agent to "upgrade the F# analyzers" in a repository that uses them.
Writing Analyzers
Checkout our Getting Started guide for analyzer authors!
How to contribute
Imposter syndrome disclaimer: I want your help. No really, I do.
There might be a little voice inside that tells you you're not ready; that you need to do one more tutorial, or learn another framework, or write a few more blog posts before you can help me with this project.
I assure you, that's not the case.
This project has some clear Contribution Guidelines and expectations that you can read here.
The contribution guidelines outline the process that you'll need to follow to get a patch merged. By making expectations and process explicit, I hope it will make it easier for you to contribute.
And you don't just have to write code. You can help out by writing documentation, tests, or even by giving feedback about this work. (And yes, that includes giving feedback about the contribution guidelines.)
Thank you for contributing!
Contributing and copyright
The project is hosted on GitHub where you can report issues, fork the project and submit pull requests.
The library is available under MIT license, which allows modification and redistribution for both commercial and non-commercial purposes.
| Product | Versions Compatible and additional computed target framework versions. |
|---|---|
| .NET | net10.0 is compatible. net10.0-android was computed. net10.0-browser was computed. net10.0-ios was computed. net10.0-maccatalyst was computed. net10.0-macos was computed. net10.0-tvos was computed. net10.0-windows was computed. |
-
net10.0
- CliWrap (>= 3.10.5)
- FSharp.Analyzers.SDK (>= 0.42.0)
- FSharp.Compiler.Service (= 43.12.402)
- Microsoft.Extensions.Logging.Console (>= 6.0.1)
- MSBuild.StructuredLogger (>= 2.3.246)
NuGet packages
This package is not used by any NuGet packages.
GitHub repositories
This package is not used by any popular GitHub repositories.
| Version | Downloads | Last Updated |
|---|---|---|
| 0.43.0 | 0 | 11/17/2026 |
| 0.42.0 | 0 | 11/16/2026 |
| 0.41.1 | 164 | 11/12/2026 |
| 0.41.0 | 5,003 | 10/16/2026 |
| 0.40.0 | 115 | 10/13/2026 |
| 0.39.2 | 2,270 | 9/12/2026 |
| 0.39.1 | 1,749 | 9/12/2026 |
| 0.39.0 | 3,173 | 9/10/2026 |
| 0.38.0 | 221 | 9/4/2026 |
| 0.37.2 | 4,552 | 6/17/2026 |
| 0.36.0 | 529 | 2/19/2026 |
| 0.35.0 | 306 | 1/24/2026 |
| 0.34.1 | 594 | 11/12/2025 |
| 0.33.1 | 316 | 10/19/2025 |
| 0.33.0 | 292 | 10/19/2025 |
| 0.32.1 | 357 | 8/2/2025 |
| 0.32.0 | 314 | 7/12/2025 |
| 0.31.0 | 360 | 5/17/2025 |
| 0.30.0 | 712 | 3/26/2025 |
| 0.29.1 | 544 | 3/7/2025 |
### Added
- [`--define` defines conditional compilation symbols for `--script` files](https://github.com/ionide/FSharp.Analyzers.SDK/pull/361), like `dotnet fsi --define`. Code under `#if SYMBOL` is type checked and analyzed only when its symbol is defined. A value that is not one symbol, such as `A;B`, is an error with exit code `20`. `--define` does not apply to `--project`, which gets its symbols from `DefineConstants`.
- [`--max-concurrent-scripts` sets how many scripts the CLI checks at the same time](https://github.com/ionide/FSharp.Analyzers.SDK/pull/361). The default is 4.
### Changed
- [The CLI checks at most 4 scripts at the same time, and releases the type check state of each script after its analysis](https://github.com/ionide/FSharp.Analyzers.SDK/pull/361). Before, it checked all scripts at once and kept the state of each script until the run ended, so memory grew by about 0.4 GB per script. In one repository, 40 scripts used 15 GB and 60 scripts used more than 16 GB. Now 284 scripts use 6 GB. `--project` inputs are unchanged.
- [A `--script` path or glob that matches no file is an error, with exit code `20`](https://github.com/ionide/FSharp.Analyzers.SDK/pull/361). Before, the CLI dropped it silently, so a typo or an unknown flag after `--script` gave a clean run that checked less than expected.
### Fixed
- [A project or script that the F# compiler service returns no check results for no longer looks type checked](https://github.com/ionide/FSharp.Analyzers.SDK/pull/361). The compiler service returns no results and no error when a type provider fails while it is set up, for example when several scripts set up FSharp.Data providers at the same time. The CLI now reports it as not type checked and runs no analyzer on it, so `--fail-on-type-errors` exits with `-5` as for other type errors.