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
I propose Fantomas prints its version at the very beginning of its execution.
The existing way to deal with this is to just separately ask for the tool version using --version.
Pros and Cons
The advantages of making this adjustment to Fantomas are:
sometimes multiple versions of the tool are installed on the machine (e.g. locally and globally) and having the version printed decreases cognitive load in these situations
this would also help maintainers since the screenshots with problems would also include the version number, reducing a need to communicate this
this is common behavior for many dotnet tools (at least in my practice)
The disadvantages of making this adjustment to Fantomas are - cannot think of any.
Extra information
Estimated cost (XS, S, M, L, XL, XXL): XS. Or XS/S if this is configurable.
Related suggestions: (put links to related suggestions here) - didn't find any.
Hmm, I'm not immediately drawn to a "yes" on this one. How many people really have this problem?
Sometimes multiple versions of the tool are installed on the machine (e.g., locally and globally), and having the version printed decreases cognitive load in these situations.
One could argue it also increases cognitive load. My initial reaction is that showing it all the time may not be that meaningful for most users.
This would also help maintainers since the screenshots with problems would include the version number, reducing the need to communicate this.
We expect folks to report issues via our online tool and would really like to discourage screenshots. The online tool allows us to verify if the problem is indeed on the latest main branch and encourages users to put effort into creating a minimal sample.
This is common behavior for many .NET tools (at least in my experience).
I wouldn’t say this reflects my experience, not with .NET tools nor other formatters.
The disadvantages of making this adjustment to Fantomas are - I can't think of any.
With frequent daily use, it holds little value, so I would prefer to list it when using --verbosity detailed.
For those reading this, please upvote this issue with 👍 if you would like to see the version by default. Downvote using 👎 if you would not prefer this.
I propose Fantomas prints its version at the very beginning of its execution.
The existing way to deal with this is to just separately ask for the tool version using
--version
.Pros and Cons
The advantages of making this adjustment to Fantomas are:
The disadvantages of making this adjustment to Fantomas are - cannot think of any.
Extra information
Estimated cost (XS, S, M, L, XL, XXL): XS. Or XS/S if this is configurable.
Related suggestions: (put links to related suggestions here) - didn't find any.
Affidavit (please submit!)
Please tick this by placing a cross in the box:
Please tick all that apply:
The text was updated successfully, but these errors were encountered: