We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
with
Issue created from fantomas-online
namespace Foo module Foo = let a = try failwith "" with // hi! :? Exception as e -> failwith ""
Fantomas was not able to produce the same code after reformatting the result.
This looks like being #1647 again, maybe? I still think the right answer here is to retain the | character, though.
|
Fantomas 4.4.0
{ config with SpaceBeforeColon = true SpaceBeforeSemicolon = true IndentOnTryWith = true }
Did you know that you can ignore files when formatting from fantomas-tool or the FAKE targets by using a .fantomasignore file?
The text was updated successfully, but these errors were encountered:
This looks indeed like #1647 but with as e as a slight deviation.
as e
I still think the right answer here is to retain the | character, though.
Yeah, working on that part from a style guide point of view first.
I'll create a follow-up issue to tackle the style change.
Sorry, something went wrong.
Trivia before bar of try with clause should indent. Fixes fsprojects#…
d0099f5
…1686.
Trivia before bar of try with clause should indent. Fixes #1686. (#1689)
2470f7a
Successfully merging a pull request may close this issue.
Issue created from fantomas-online
Formatted code
Reformatted code
Problem description
Fantomas was not able to produce the same code after reformatting the result.
This looks like being #1647 again, maybe?
I still think the right answer here is to retain the
|
character, though.Extra information
Options
Fantomas 4.4.0
Did you know that you can ignore files when formatting from fantomas-tool or the FAKE targets by using a .fantomasignore file?
The text was updated successfully, but these errors were encountered: