-
Notifications
You must be signed in to change notification settings - Fork 14
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
trailing commas followup #299
Comments
Assigned Dale as the coordinator. Multiple people will be involved of course in checking all items off of this list |
For anyone interested, I made a scalafix rewrite to insert missing trailing commas. Here's the diff from running the rewrite on a large corpus olafurpg/scala-repos#19 it's still a WIP, it might be nice to limit the rewrite to varargs (slow, but doable with the new semantic rewrites) or a configured whitelist of term applications such as |
@olafurpg Does scalafmt have a PR yet? |
Not yet. Scalafmt is still on meta 1.4, will wait for 1.6 which is due next week. |
@SethTisue this is on the top of my out-of-hours TODO list. Lemme know if you need me to fast track it for 2.12.2 and I can try speaking to @eed3si9n. |
Scalariform doesn't even have a 2.12 release at all afaik (scala-ide/scalariform#235), so that one isn't a blocker presumably the spec and SIP updates will be merged so perhaps the only pressing thing here is to make sure JetBrains is aware and has this in their pipeline for IntelliJ...? |
Cool. I'm working on that. It's tracked on their end as https://youtrack.jetbrains.com/issue/SCL-10597. Thankfully @jastice might be able to help me with advise and tips. |
It would appear that not only does Scalariform not have a 2.12 release, but Scalariform is at this time dead, looking for new maintainers. So I'm dropping it completely from the checklist. |
(removed from the 2.12.2 milestone since the remaining piece isn't absolutely essential for 2.12.2) |
@Lugzan, of JetBrains, has implemented trailing commas in IntelliJ Scala! Updated the checklist. |
TODO:
The text was updated successfully, but these errors were encountered: