Vanity alignment used when calling base constructor

[knocte]

Issue created from fantomas-online

Code

type public DerivedExceptionWithLongNaaaaaaaaameException (message: string,
                                                           code: int,
                                                           originalRequest: string,
                                                           originalResponse: string) =
    inherit BaseExceptionWithLongNaaaameException(message, code, originalRequest, originalResponse)

Result

type public DerivedExceptionWithLongNaaaaaaaaameException
    (
        message: string,
        code: int,
        originalRequest: string,
        originalResponse: string
    ) =
    inherit BaseExceptionWithLongNaaaameException(message,
                                                  code,
                                                  originalRequest,
                                                  originalResponse)

Expected results?

type public DerivedExceptionWithLongNaaaaaaaaameException
    (
        message: string,
        code: int,
        originalRequest: string,
        originalResponse: string
    ) =
    inherit BaseExceptionWithLongNaaaameException
        (
            message,
            code,
            originalRequest,
            originalResponse
        )

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 at 02/11/2021 13:26:01 - 7783b6f

    { config with
                MaxLineLength = 80 }

[kevingentile]

I'm seeing a similar unexpected alignment with the following:

type ChildTestType() =
    inherit ParentTestType(System.IO.Path.Combine(Environment.CurrentDirectory, "myfile.yml"))

formats as:

type ChildTestType() =
    inherit ParentTestType(System.IO.Path.Combine(
        Environment.CurrentDirectory,
        "myfile.yml"
    ))

which yields an incorrect indentation error by the compiler.

[knocte]

@kevingentile if it yields a compilation error then your bug is not the same as this, because this one was classified as minor (stylistic), while yours could be classified as higher priority. So please file a new bug.