-
Notifications
You must be signed in to change notification settings - Fork 23
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
Suggestion: add option for first parameter to be on same line #18
Comments
EWWWWWWWWWWWWWWWW |
But sure, I'll add a preference. Need to figure out how to share data between the main app and the extension though... |
I hate it too, just looking out for others 😎 |
I can foresee some other options being added in future so wouldn't be a bad idea to figure it out. And another reason why unit tests will become increasingly useful if more options get added. |
Just wanted to create the same suggestion but it already exists. Only one clarification - not only the first parameter shouldn't be on a separate line, but also the closing round bracket. With the current implementation we will get this formatting: ClickableCard(
image: "",
title: "",
value: "",
action: { }
) My proposition to have an option for this: ClickableCard(image: "",
title: "",
value: "",
action: { }) |
That's what my example already shows but I can amend the request wording to be explicit. |
While I am actually a fan of Multiliner's current formatting behavior, some people might prefer not having a line-break between the method name and the first parameter.
Current Behavior
Proposed opt-in behavior (as a preference)
First parameter starts on the same line, and closing parens trails immediately after the last parameter.
The text was updated successfully, but these errors were encountered: