XML Doc comments on DU cases seem to get shuffled

[baronfel]

Issue created from fantomas-online

Code

/// Represents reasons why a text document is saved.
type TextDocumentSaveReason =
/// Manually triggered, e.g. by the user pressing save, by starting debugging,
/// or by an API call.
| Manual = 1

/// Automatic after a delay.
| AfterDelay = 2

/// When the editor lost focus.
| FocusOut = 3

Result

/// Represents reasons why a text document is saved.
type TextDocumentSaveReason =
    /// Manually triggered, e.g. by the user pressing save, by starting debugging,
    /// or by an API call.
    | Manual = 1
    /// Automatic after a delay.
    |

    AfterDelay = 2
    /// When the editor lost focus.
    |

    FocusOut = 3

Problem description

Found this while converting Ionide.LanguageServerProtocol to use Fantomas. The formatting errors cause compilation problems because there's no indent after the second and third pipes and their respective DU cases. The Newlines after the pipe are also not-ideal, but that's minor compared to the compilation issue.

Extra information

• The formatted result breaks by code.
• The formatted result gives compiler warnings.
• I or my company would be willing to help fix this.

Options

Fantomas master branch at 2022-04-04T14:08:13Z - e784cd6

Default Fantomas configuration

_{Did you know that you can ignore files when formatting from fantomas-tool or the FAKE targets by using a .fantomasignore file?}

[nojaf]

Hello, this rings a bell and looks similar to #2155.
I have a script ready for another YouTube video to solve this one.
In short, you want to correct the range of SynEnumCase in case there is a bar and/or XML comment.
How annoying is this bug for you? If it is a blocker I can just solve it easily, otherwise, I'd like to wait a bit until I can make that recording. Speak your mind please, I'm ok with either outcome.

[baronfel]

No rush, it's not critical. A video is a great idea 😊