ionide/FSharp.Analyzers.SDK

Issues

• Improve editor UX

  #209 opened 2 months ago by nojaf
  0

• Add a `-p` flag to allow passing MSBuild properties through to the MSBuild evaluation portion of checking.

  #84 opened 4 months ago by baronfel
  3

• Have Include/ExcludeFilter warn if an input glob didn't match any analyzers

  #203 opened 4 months ago by Smaug123
  2

• Add cancleation token for the analyzer

  #19 opened 4 months ago by Krzysztof-Cieslak
  1

• Add whitelisting parameter to CLI

  #79 opened 5 months ago by dawedawe
  1

• NuGet vulnerability warnings from transitive dependencies of FSharp.Analyzers.Build

  #191 opened 5 months ago by Numpsy
  6

• Default branch name

  #81 opened 5 months ago by nojaf
  2

• Testing story for a local project

  #186 opened 6 months ago by nojaf
  0

• Please add License to fsharp-analyzers dotnet tool publication

  #33 opened 6 months ago by DamianAtWork
  8

• FsLex files are reported without their path

  #179 opened 6 months ago by dawedawe
  0

• Sarif file should not report absolute file paths

  #154 opened 7 months ago by nojaf
  1

• --project value should be tested if path exists

  #141 opened 7 months ago by nojaf
  0

• Accept multiple folders as analyzer input path

  #111 opened 7 months ago by nojaf
  2

• Provide better DX when project cracking failed

  #126 opened 7 months ago by nojaf
  0

• Community analyzers project

  #133 opened 7 months ago by nojaf
  4

• Log project that is about to run in verbose mode

  #125 opened 7 months ago by nojaf
  0

• Create sarif folder if it does not exist

  #132 opened 7 months ago by nojaf
  0

• Analyzer cannot use FSharp.Core 8

  #124 opened 8 months ago by nojaf
  0

• Add inspect sub command

  #123 opened 8 months ago by nojaf
  0

• Analyzer report

  #110 opened 8 months ago by nojaf
  0

• Could not load file or assembly FSharp.Compiler.Service

  #22 opened 8 months ago by halcwb
  0

• Cli option --fail-on-all-warnings

  #118 opened 8 months ago by dawedawe
  1

• Exclude analyzers

  #112 opened 8 months ago by nojaf
  1

• Support multiple project parameters in the Cli tool

  #113 opened 8 months ago by dawedawe
  0

• Add documentation about unit testing

  #96 opened 9 months ago by nojaf
  0

• Add a SDK.Tests package

  #18 opened 9 months ago by TheAngryByrd
  3

• Does the SDK discriminate between debug/release mode? Does it matter?

  #68 opened a year ago by cmeeren
  1

• Allow analyzers to process .fsi files

  #78 opened 9 months ago by dawedawe
  0

• Directions in readme don't seem to work

  #66 opened a year ago by bigjonroberts
  2

• Surface FSharpCheckFileResults in Context

  #67 opened 9 months ago by cmeeren
  1

• Allow disabling analyzers for line/file/etc.

  #47 opened a year ago by cmeeren
  6

• One analyzer with multiple messages/codes, or multiple analyzers?

  #60 opened a year ago by cmeeren
  0

• Proposal: More flexible Analyzer probing rules

  #32 opened 3 years ago by baronfel
  1

• Use same severity levels as Roslyn analyzers

  #59 opened a year ago by cmeeren
  0

• Modernize/simplify tooling/CI/packaging?

  #49 opened a year ago by cmeeren
  5

• How to traverse AST in analyzers?

  #44 opened a year ago by cmeeren
  5

• What is Message.Type used for?

  #48 opened a year ago by cmeeren
  2

• What's the story for breaking changes in FCS when using FSharp.Analyzers.SDK?

  #46 opened a year ago by cmeeren
  6

• Can analyzers be run as a dotnet tool?

  #45 opened a year ago by cmeeren
  2

• List publicly-available F# analyzers somewhere

  #43 opened 2 years ago by StachuDotNet
  0

• CLI fails on projects that contain FSI signature files

  #37 opened 3 years ago by enovales
  1

• RunSample failed to run on macOS

  #36 opened 3 years ago by objectx
  2

• Current Analyzers CLI needs to bundle msbuild locator

  #34 opened 3 years ago by baronfel
  3

• Bump framework target to netcoreapp3.1

  #17 opened 3 years ago by aaronpowell
  5

• Update to net5

  #29 opened 3 years ago by tforkmann
  7

• Make F# Analyzer API independent of FCS?

  #28 opened 4 years ago by dsyme
  7

• Visual Studio 2017/2019 support?

  #23 opened 4 years ago by Thorium
  11

• Make fixes lazy

  #27 opened 4 years ago by deviousasti
  0

• Rename to FSharp.Analysers.SDK ?

  #24 opened 4 years ago by Thorium
  2

• Add ability to return tooltips from analyzer

  #20 opened 4 years ago by Krzysztof-Cieslak
  0