-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Use Simulacrum Scalafix #3424
Use Simulacrum Scalafix #3424
Conversation
Codecov Report
@@ Coverage Diff @@
## master #3424 +/- ##
==========================================
- Coverage 92.65% 91.54% -1.12%
==========================================
Files 379 379
Lines 7994 8209 +215
Branches 227 227
==========================================
+ Hits 7407 7515 +108
- Misses 587 694 +107
Continue to review full report at Codecov.
|
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.
I'm usually against checked in generated source, but I feel better after rereading the linked ticket. I think this is our best option at present. 👍
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.
I like this approach.
haven't added this process to the validateJVM task yet,
Just curious, so the plan is to have validateJVM generate code and add commits to PRs from CI?
@kailuowang I think API changes that map over to codegen changes will be infrequent enough that we can run it manually for now. If it turns out that that's not the case and we're getting a lot of PRs with missing codegen changes, we could tie these tasks into I guess we could also have something more automated in CI, but that seems unnecessary for something that's likely to happen once every month or two. |
Thanks all! I'm merging this with a merge commit to keep the automated changes separate from the configuration that sets them up. I'll update the Dotty cross-building branch later today or tomorrow. |
Addresses #3192, using a new release of Simulacrum Scalafix. An earlier version of this change was included in #3269, but I think it should be reviewed and merged separately from the Dotty cross-build work (we'll need to decide which Dotty version to support, since for example there's still no official 0.23 or 0.24 release of the scalatestplus dependency, but I don't think that should block this change).
The Scalafix commit was generated by running the following commands:
These commands will need to be run manually after any API change that needs syntax support. I haven't added this process to the
validateJVM
task yet, but they're idempotent and only take a few seconds, so I guess we could run them on every build.