-
Notifications
You must be signed in to change notification settings - Fork 277
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
ConvertToNewScala3Syntax: use the new granular parameter #3735
Conversation
f4e22be
to
ab73a5c
Compare
Do we really need this to be that granular? Maybe it's enough to have separate changes for optional braces and separate for things that are not affected by it? |
@tgodzik i thought about it. looked at braces rewrite which has over time become rather granular, same for indent which had originally been declared inviolate and fixed, and decided to avoid further requests 🙂 |
I think in this case we should not allow to have different if and when convention. But it's up to you, I don't think it would ever make sense and it would be valid to close any such request as not planned. |
@tgodzik agreed, let's merge |
also, since i am not a big expert on backports to scala213 (via |
ifCond: Boolean = true, | ||
whileCond: Boolean = true, | ||
forEnum: Boolean = true, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ifCond: Boolean = true, | |
whileCond: Boolean = true, | |
forEnum: Boolean = true, | |
optionalBraces = true |
varargStar: Boolean = true, | ||
importStar: Boolean = true, | ||
importAs: Boolean = true, | ||
typeWildcardQuestionMark: Boolean = true, | ||
typePlaceholderUnderscore: Boolean = true |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
varargStar: Boolean = true, | |
importStar: Boolean = true, | |
importAs: Boolean = true, | |
typeWildcardQuestionMark: Boolean = true, | |
typePlaceholderUnderscore: Boolean = true | |
deprecatedSyntax = true |
maybe? This would be controlled by the dialect to see if the new syntax is allowed.
Otherwise if only one thing is set then the user will be quite confused. The separate non optional braces (traditional braced if etc.) will probably not be deprecated ever,.
@tgodzik all done |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
Supersedes #3732.