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
We'd like to pull in a dependency on Fantomas for the dotnet-format tool (tracking issue: dotnet/format#39).
Technically it would be straightforward to do, since the tool just does some orchestration of the C# and VB code formatters today, and it would just shell out to Fantomas when encountering F# projects. But there is a question on policy, which I propose as follows:
Issues for F# formatting are moved to this repo
Since Fantomas is an OSS project, there is no support policy that either Microsoft or Fantomas maintainers must adhere to
@jindraivanek sounds great! Just wanted to make sure it was fine to package fantomas inside another global tool. I'll make sure that people posting on the dotnet/format repo know to file bugs on http://ratatosk.dynu.net/fantomas if they are fantomas specific
The main thing is it may be reasonable to expect more bugs coming in as this does open up fantomas to more use. Just wanted to make sure that was okay 🙂
I'll close the issue as we'll take care of thing on the dotnet-format side. Let us know if you have any further questions/concerns!
We'd like to pull in a dependency on Fantomas for the dotnet-format tool (tracking issue: dotnet/format#39).
Technically it would be straightforward to do, since the tool just does some orchestration of the C# and VB code formatters today, and it would just shell out to Fantomas when encountering F# projects. But there is a question on policy, which I propose as follows:
Thoughts? cc @jmarolf
The text was updated successfully, but these errors were encountered: