[style-guide] Option branches are always indented when piping into `function` keyword about fslang-design HOT 2 CLOSED

Hello, thank you for your interest in this project.
Some initial feedback:

• You marked that this is part of the G-Research style guide although the guide does not provide any guidance from this specific case. You made an assumption that the same rules apply for function and match and how they should work in combination with the pipe infix operator. I'm sorry but this is insufficient as a basis for disucussion. Please open an issue in both style guides (MS & GR) so that this question can first be resolved over there.
• If both style guides suggest something different than what Fantomas has today, we can change the style here. Please read more about this in our contribution guidelines. Fantomas only changes style if new information presents itself in the style guides.
• The reason why the behaviour changed from 4.4 appears to be fsprojects/fantomas#1559, perhaps we missed something while solving this.
• Fantomas does not guarantee the exact same output between versions. It evolves as style guides evolve, so the argument about the git diffs does not stand.

from fslang-design.

On the style guide question here - the code listed is sufficiently non-idiomatic that I don't think its formatting should deviate from the norms, the indentation is fine and does make the code easier to read (though less likely that construct will be used, which is fine). I'll close this

from fslang-design.