Supports configurable, Eclipse like, save actions, including "optimize imports", "reformat code", "rearrange code", "compile file" and some quick fixes like "add / remove 'this' qualifier", etc. The plugin executes the configured actions when the file is synchronised (or saved) on disk.
Using the save actions plugin makes your code cleaner and more uniform across your code base by enforcing your code style and code rules every time you save. The settings file (see files location) can be shared in your development team so that every developer has the same configuration.
The code style applied by the save actions plugin is the one configured your settings at "File > Settings > Editor > Code Style". For some languages, custom formatter (Dartfmt, Prettier, etc.) may also be triggered by the save actions plugin. See the Editor Actions configuration for more information.
Thank you to JetBrains for supporting the Save Actions plugin: they provide an open-source license, which is necessary to build, test and deploy this plugin. Check out their products at https://www.jetbrains.com.
Works in JetBrains IDE with Java support, like Intellij IDEA and AndroidStudio.
.epfsupport (see Eclipse support)
Install it from your IDE (Intellij IDEA, PyCharm, etc.):
All versions of the plugin are available from the JetBrains plugin repository. You can download the jar and add it to your IDE (you won't get updates thought):
The plugin can trigger automatically or manually on IDE actions (standard actions) or plugin actions. Most actions needs to be enabled individually (see activation).
The plugin will trigger automatically on any of these IDE actions (needs to be activated with "Activate save actions on file save" in activation)):
The plugin actions are grouped under the menu "Code > Save Actions". You can associate a keymap to any action in "Settings > Keymap > Search 'save actions'".
The configurations are located in "File > Settings > Other Settings > Save Actions".
You can quickly toggle the plugin activation by using the "Enable Save Action" action. Use "CTRL + SHIFT + A" then search for it. It will also show if it is currently activated or not.
|Activate save actions on file save||Enable / disable the plugin on file save. Before saving each file, it will perform the configured actions below|
|Activate save actions on shortcut||Enable / disable the plugin on shortcut, by default "CTRL + SHIFT + S" (configured in "File > Keymaps > Main menu > Code > Save Actions")|
|Activate save actions on batch||Enable / disable the plugin on batch, by using "Code > Save Actions > Execute on multiple files"|
|No action if compile errors||Enable / disable no action if there are compile errors. Applied to each file individually|
|Optimize imports||Enable / disable import organization (configured in "File > Settings > Code Style > Java > Imports")|
|Reformat file||Enable / disable formatting (configured in "File > Settings > Code Style"). See "Reformat only changed code" for more options|
|Reformat only changed lines||Enable / disable formatting for only changed lines, which will work only if a VCS is configured|
|Rearrange fields and methods||Enable / disable re-ordering of fields and methods (configured in "File > Settings > Code Style > Java > Arrangement")|
|[experimental] Compile file||Enable / disable compiling of the modified file. The compiler might compile other files as well. Warning: this feature is experimental, please post feedback in the github issues|
|[experimental] Reload file||Enable / disable reloading of the files in the running debugger, meaning the files will get compiled first. The compiler might compile other files as well. Warning: this feature is experimental, please post feedback in the github issues|
|[experimental] Execute action||Enable / disable executing of an action using quick lists (using quick lists at "File > Settings > Appearance & Behavior > Quick Lists"). See Editor Actions for more information Warning: this feature is experimental, please post feedback in the github issues|
Some languages requires specific actions, such as Dartfmt or Prettier:
Using the "Execute action" configuration, the plugin can launch arbitrary editor actions. While not all actions will work, it can be used to launch external tools, specific runs, etc. This feature is experimental, you can post your feedback on issue #118.
The actions are implemented in the form of "quick lists", an IDE function that is used to define a list of actions that can be then executed. Quick lists can be configured at "File > Settings > Appearance & Behavior > Quick Lists", and once configured, one can be selected and used in the plugin, using the "Execution action" configuration drop down list.
|File path inclusions||Add / remove file path inclusions (by default, everything included). The Java regular expressions match the whole file name from the project root. Include only Java files:
|File path exclusions||Add / remove file path exclusions to ignore files (overrides inclusions). The Java regular expressions match the whole file name from the project root. Exclude 'Main.java' only in root folder:
|Use external Eclipse configuration||Add external configuration file ".epf" to read settings from. This will update the current settings and use only the ".epf" file content. Use "reset" button to remove|
If a quick fix adds something that is removed by another quick fix, the removal wins.
|Add final modifier to field||The field
|Add final modifier to local variable or parameter||The local variable
|Add final modifier to local variable or parameter except if implicit||The local variable
|Add static modifier to methods||The method
|Add this to field access||The access to instance field
|Add this to method access||The access to instance method
|Add class qualifier to static member access||The access to class field
|Add class qualifier to static member access outside declaring class only||The access to class field
|Add missing @Override annotations||The method
|Add blocks to if/while/for statements||The statement
|Add missing serialVersionUID field for Serializable classes||The class
|Remove unnecessary this to field and method||The access to instance field
|Remove final from private method||The method
|Remove unnecessary final to local variable or parameter||The local variable
|Remove explicit generic type for diamond||The list creation
|Remove unused suppress warning annotation||The annotation
|Remove unnecessary semicolon||The statement
|Remove blocks from if/while/for statements||The statement
|Change visibility of field or method to lower access||The field
Built for SDK version 2016.3, 2018.3, 2019.3, using JDK 8, those are the currently supported products, and is not expected to work in other products:
See issue #18 for a beta packaging that you can try in other products.
The save-actions plugin supports Eclipse configuration
.epf files by the Workspace Mechanic Eclipse plugin (Java IDE only). You can specify a path to an Eclipse configuration file in the "Eclipse support" settings section to import it. The plugin will load the content of the file in the plugin configuration, and disable the plugin configuration options (the checkbox will be grayed out). Use the "reset" button to remove the import.
The plugin will stay in sync with your Eclipse configuration file. Not every features are present on either side, but the ones that are in common are supported.
You can find an example of an Eclipse configuration
.epf file in the test resources.
# @title Save Actions # @description Save Actions # @task_type LASTMOD file_export_version=3.0 /instance/org.eclipse.jdt.ui/editor_save_participant_org.eclipse.jdt.ui.postsavelistener.cleanup=true /instance/org.eclipse.jdt.ui/sp_cleanup.format_source_code=true /instance/org.eclipse.jdt.ui/sp_cleanup.format_source_code_changes_only=false /instance/org.eclipse.jdt.ui/sp_cleanup.organize_imports=true /instance/org.eclipse.jdt.ui/sp_cleanup.remove_trailing_whitespaces=true ...
Some things to note when using other plugins with the Save Actions plugin:
:wto save in IdeaVim won't trigger the plugin, but using
:wawill, since it calls the "Save All" action. See issue #222).
com.dubreuia.SaveActionManager. If you are using default locations, it would be in
.ideafolder. That file can be committed in git thus shared in your development team. If you are using the default locations, it would be in
There are 2 boards to track the issues (bug or features):
When you submit an issue, it will be triaged into either board.
Big thanks to all the contributors submitting issues, testing, and especially submitting pull requests. See contributors graph ♥️