Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fantomas adds "of" to a union case when it is seemingly _too long_ #1796

Closed
1 of 3 tasks
Zaid-Ajaj opened this issue Jun 29, 2021 · 1 comment · Fixed by #1797
Closed
1 of 3 tasks

Fantomas adds "of" to a union case when it is seemingly _too long_ #1796

Zaid-Ajaj opened this issue Jun 29, 2021 · 1 comment · Fixed by #1797

Comments

@Zaid-Ajaj
Copy link

Issue created from fantomas-online

Code

type TransactionType = 
    | [<CompiledName "External Credit Balance Refund">] ExternalCreditBalanceRefund
    | [<CompiledName "Credit Balance Adjustment (Applied from Credit Balance)">] CreditBalanceAdjustmentAppliedFromCreditBalance

Result

type TransactionType =
    | [<CompiledName "External Credit Balance Refund">] ExternalCreditBalanceRefund
    | [<CompiledName "Credit Balance Adjustment (Applied from Credit Balance)">] CreditBalanceAdjustmentAppliedFromCreditBalance of

Problem description

Fantomas adds "of" to a union case when it is seemingly too long

The second union now has of at the end of the second union without types which breaks the generated code

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 06/28/2021 08:27:00 - 31fc949

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
Copy link
Contributor

nojaf commented Jun 30, 2021

Thank you for reporting this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants