-
Notifications
You must be signed in to change notification settings - Fork 136
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
Stop suggesting the save actions plugin #2547
Conversation
Generate changelog in
|
Makes sense to me. First removing this suggestion, and following up with a replacement that configures native IntelliJ "Actions on save" works nicely. |
Related: palantir/palantir-java-format#862 |
Released 5.5.0 |
This addresses #2545 |
###### _excavator_ is a bot for automating changes across repositories. Changes produced by the roomba/latest-baseline-oss check. # Release Notes ## 5.5.0 | Type | Description | Link | | ---- | ----------- | ---- | | Fix | No longer suggest the "Save Actions" IntelliJ plugin which does not work in IntelliJ 2023.1 for use with Palantir Java Format. Instead, Palantir Java Format will support the IntelliJ native "Actions on save" reformat capability in a future release. | palantir/gradle-baseline#2547 | To enable or disable this check, please contact the maintainers of Excavator.
Before this PR
The save actions plugin is broken in IntelliJ 2023.1. It is unmaintained and there is no official fix.
In 2021.2, IntelliJ introduced a new built in reformat on save feature.
After this PR
==COMMIT_MSG==
No longer suggest the "Save Actions" IntelliJ plugin which does not work in IntelliJ 2023.1 for use with Palantir Java Format. Instead, Palantir Java Format will support the IntelliJ native "Actions on save" reformat capability in a future release.
==COMMIT_MSG==
Possible downsides?
Why this code is in gradle-baseline rather than the palantir-java-format gradle plugin I do not understand. It's going to make fixing this issue quite a bit harder.