Bump fantomas and fsharp-analyzers

[dependabot]

Updated fantomas from 7.0.1 to 7.0.3.

Release notes

Sourced from fantomas's releases.

7.0.3

7.0.3

Fixed

• Application in indexed set should not be multiline. #​1999

Special thanks to @​Numpsy and @​nojaf!

https://www.nuget.org/packages/fantomas/7.0.3

7.0.2

7.0.2

Changed

• Print version at beginning of execution when detailed verbosity is set. 3148

Fixed

• Anonymous records in interpolated strings. #​3162
• Preserve backticks in active pattern idents. #​3126
• New lines are added after comment in measure type. #​3145
• Idempotency problem with comments in applications on lambda expressions. #​3128

Special thanks to @​alex-de-oliveira and @​dawedawe!

https://www.nuget.org/packages/fantomas/7.0.2

Commits viewable in compare view.

Updated fsharp-analyzers from 0.30.0 to 0.32.0.

Release notes

Sourced from fsharp-analyzers's releases.

0.32.0

Added

• Support script (fsx) files (thanks @​TheAngryByrd!)

Changed

• Add project options to analyzer contexts (Thanks @​Numpsy!)

0.31.0

Changed

• Update FSharp.Compiler.Service to 43.9.300 (Thanks @​Numpsy!)
• Update Ionide.ProjInfo.ProjectSystem package version to 0.71.0 (Thanks @​TheAngryByrd!)

Commits viewable in compare view.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.

[Smaug123]

(If you were closing/reopening to rerun the pipelines, the problem is that the analysers also need to be bumped.)

[nojaf]

It makes me wonder if the frequency of these updates is slightly too high. Updating these analysers and Fantomas every quarter might be sufficient as well.

[Smaug123]

Agreed, I suspect we can turn Dependabot down here.

I suppose the ultimate source of the backward-incompatibility is that the SDK uses types from FSharp.Compiler.Services which are liable to change as upgrades happen, and there's no easy way to ship multiple versions of FCS in the analyser SDK at the same time. It doesn't seem to me that those types should need to change very often, though; having some kind of highly-backward-compatible shim between FCS and the analyser SDK would be annoying but I predict it would reduce this churn a lot.

[nojaf]

I suppose the ultimate source of the backward-incompatibility is that the SDK uses types from FSharp.Compiler.Services which are liable to change as upgrades happen

Yup, very much! However, since analysers never quite gained traction in the community, determining the surface area of a stable, decoupled API from FCS is challenging.

I'm also curious if a group entry for the tool and NuGet package would be effective. You could do something like this:

groups:
  analyzers:
    patterns:
      - "fsharp-analyzers"
      - "G-Research.FSharp.Analyzers"

I'm unsure if this approach would work, given that one is a tool and the other is a regular NuGet package.