Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Before this PR
In #862, we moved away from using the "Save Actions" plugin to using the native IntelliJ "Actions on Save" feature.
An oversight when doing this was that the Save Actions plugin was configured to use optimise imports as well. However, in #862 we did not enable optimise on save.
This mostly flew under the radar as most devs have manually enabled the "Optimize Imports on the Fly" option in intellij at soe point in the last $years, and this mostly fixes the inputs for you as you code. However, some devs do not have this, especially devs who are new or are low code who are least equipped to resolve this problem.
After this PR
==COMMIT_MSG==
Ensure imports are optimised on save, as well as formatting.
==COMMIT_MSG==
Possible downsides?