[Feature request] Flag for an explicit path to the configuration file (editorconfig)

[njlr]

I propose we add a CLI flag for explicit path to a configuration file (.editorconfig)

The existing way of Fantomas deals with this problem is ... rearrange files

Pros and Cons

The advantages of making this adjustment to Fantomas are ... it makes it easier to use Fantomas in certain build systems, such as Bazel

The disadvantages of making this adjustment to Fantomas are ... a small amount of extra code

Examples

dotnet fantomas --config ./somewhere/else/.editorconfig ./Hello.fs

Extra information

Estimated cost (XS, S, M, L, XL, XXL): S

Related suggestions: (put links to related suggestions here)

Affidavit (please submit!)

Please tick this by placing a cross in the box:

• [x] I have read the Contribution Guidelines.
• [x] I have searched both open and closed suggestions on this site and believe this is not a duplicate

Please tick all that apply:

• [x] This is not a breaking change to Fantomas
• [x] I or my company would be willing to help implement and/or test this
• [ ] This suggestion is part of the Microsoft style guide (please add a link to section if so)
• [ ] This suggestion is part of the G-Research style guide (please add a link to section if so)

[nojaf]

Hello, this is a bit of a weird request given the nature of how .editorconfig works. Could you elaborate on what is not working in your situation?

[nojaf]

Closing due to lack of activity.