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

#1627 [06]: Router: ignore line breaks for config style apply #1786

Merged
merged 6 commits into from
Mar 17, 2020

Conversation

kitbellew
Copy link
Collaborator

@kitbellew kitbellew commented Mar 15, 2020

For the purposes of this change, config style would mean a newline after the opening parenthesis and one argument per line. Whether the closing parenthesis is dangling can be controlled via the danglingParentheses parameter.

NB: there might be other places where config style is checked, they will be addressed separately.

Helps with #1627.

@kitbellew
Copy link
Collaborator Author

@olafurpg @tanishiking @poslegm PTAL

@kitbellew kitbellew requested a review from poslegm March 17, 2020 06:26
case EndpointActivated(`endpoint`) ⇒ endpoint
case EndpointFailedToActivate(`endpoint`, cause) ⇒ throw cause
})
<<< SKIP 3.27 enclosed in block, def, chain follows
Copy link
Collaborator

@poslegm poslegm Mar 17, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are you planning to remove SKIP in the next PRs before release?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yes, it needs a matching change handling unfold in select chains

1. reduce indent to 2 and de-indent earlier in binPack.unsafeCallSite
2. anticipate dangle when comment/NL precede closing paren
3. in infix with parens, recognize newline after single-line comment
   and set correct indent and dangle
The original naming reflected the side of FormatToken which will be used
to find the expiration token but it conflicted with the two more common
types deriving from util.Either and was not intuitive to use.
For the purposes of this change, config style would mean a newline after
the opening parenthesis and one argument per line. Whether the closing
parenthesis is dangling can be controlled via the danglingParentheses
parameter.

NB: there are other places where config style is checked, they will be
addressed separately.
@kitbellew kitbellew merged commit e1bbdfc into scalameta:master Mar 17, 2020
@kitbellew kitbellew deleted the 1786 branch March 17, 2020 13:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants