You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was wondering if there were any plans, or existing discussions (I didn't see any with a quick search of the issues on this repo) around handling the location of closing parenthesis for function calls.
So for the slice and map instance, the closing brace is forced on a newline with a trailing comma added as need. What do you think about making this also be the case for the closing parenthesis on multi-line function calls? So that both calls to foo above would be formatted as:
foo(
"wat",
"hmm",
"something",
)
The text was updated successfully, but these errors were encountered:
matthewhughes934
changed the title
Handling of closing parenthesis on function calls
Feature: Handling of closing parenthesis on function calls
Jul 25, 2023
Hi, thanks for creating this tool.
I was wondering if there were any plans, or existing discussions (I didn't see any with a quick search of the issues on this repo) around handling the location of closing parenthesis for function calls.
To demonstrate my thoughts:
The result of
diff -U1 file.go <(gofumpt file.go)
:So for the slice and map instance, the closing brace is forced on a newline with a trailing comma added as need. What do you think about making this also be the case for the closing parenthesis on multi-line function calls? So that both calls to
foo
above would be formatted as:The text was updated successfully, but these errors were encountered: