You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In #836, we introduced a whole new brave world of choosing your own Fantomas version.
These last weeks, we've published two new versions of Fantomas that are also compatible with Ionide.
The question remains, how do we want to inform the user of these updates?
We can easily detect new versions via the NuGet API:
But how do we want to deal with this?
Some people will be interested in every version (alpha, beta, stable), while others will only care for revisions or minors.
The text was updated successfully, but these errors were encountered:
In an ideal world, I think the user should be prompted:
once per repo
per stable version only
with an option to ignore the version specified
all of this is stuff that would probably live at the ionide/FSAC layers and not necessarily in the Fantomas.Client library itself (aside from maybe exposing an API to check the current version and query for the latest Fantomas version specifically), and might be conditioned behind a config flag like fsharp.fantomas.updateCheck: true|major|minor|patch|prerelease|ignore or something.
In #836, we introduced a whole new brave world of choosing your own Fantomas version.
These last weeks, we've published two new versions of Fantomas that are also compatible with Ionide.
The question remains, how do we want to inform the user of these updates?
We can easily detect new versions via the NuGet API:
But how do we want to deal with this?
Some people will be interested in every version (alpha, beta, stable), while others will only care for revisions or minors.
The text was updated successfully, but these errors were encountered: