Managing Code Style on a Directory Level with EditorConfig

As we announced a short while ago, in the upcoming version 2019.2, IntelliJ IDEA and other IntelliJ-based IDEs are extending EditorConfig support, thus allowing you to manage all code style settings for each set of files individually. All you need to do is place an .editorconfig file in the root directory containing the files whose code style you want to define. You can have as many .editorconfig files within a project as needed, so you can specify different code styles for different modules. All options from the .editorconfig file are applied to the directory where it resides as well as all of its sub-directories on top of the current project code style defined in Settings/Preferences | Editor | Code Style. If anything is not defined in .editorconfig, it’s taken from the project settings.

In v2019.2, in addition to the standard EditorConfig options, we are adding a bunch of custom IntelliJ IDEA options, so now you can conveniently manage all your code style settings on the directory level.

The options are divided into the following categories:

  • Standard options such as indent_size, indent_style, and so on. These options do not have any domain-specific prefixes.
  • Generic IntelliJ IDEA options that have the ij_ prefix and are applicable to all languages:
    • ij_visual_guides
    • ij_formatter_off_tag
    • ij_formatter_on_tag
    • ij_formatter_tags_enabled
    • ij_wrap_on_typing
    • ij_continuation_indent_size
    • ij_smart_tabs
  • Common IntelliJ IDEA language options supported by many (but not all) languages. They start with the ij_any prefix, for example, ij_any_brace_style.
  • IntelliJ IDEA language-specific options starting with the ij_<lang>_ prefix where <lang> is the language domain ID (normally a lower-case language name). For example, ij_java_blank_lines_after_imports.

Note: The same options may be defined as a common option and a language-specific option, for example, ij_<...>_brace_style. Language-specific options have higher priority over common or generic options.

Try it Out
Let’s give this feature a try using the ij_visual_guides option.

  1. In the Project view, select a source directory and select New | EditorConfig File from the context menu:
    create_new_editorconfig
  2. To create an empty file, do not select any properties in the dialog that opens: editorconfig_properties
  3.  Add the following line: ij_visual_guides = 40,60 (once you start typing, code completion will suggest the available properties). You will immediately see visual guides appear at columns 40 and 60:
    editorconfig_visual_guides

Preview Code Style Settings

You can now easily preview how changes to your code style settings will impact the actual source files. To do this, click the eye icon in the left gutter of the EditorConfig file and select a source file affected by it. The preview of this file will open on the right:

editorconfig_preview_changes

You can make changes in the Preview pane to try and test how your configuration changes are reflected without worrying about making unwanted changes to the source code  all these changes are discarded when the EditorConfig file is closed.

If you’re excited to try this feature right now without having to wait for the release, download a new IntelliJ IDEA 2019.2 EAP build right now from our website or update using the ToolBox App.

Please share your feedback with us here in the comments section, in our issue tracker, or on Twitter.

Happy Developing!

This entry was posted in New Features and tagged , . Bookmark the permalink.

13 Responses to Managing Code Style on a Directory Level with EditorConfig

  1. R. G. says:

    Great that there will support for changes in the editor but I think that this example is way limited. I personally don’t see that this post adds anything with content to the blog. :)

    Is it because you expect us to ask what do we want to see?
    Is that a real world use case of editorconfig?

    • Anna Gasparyan says:

      This example merely illustrates how configuration changes can be previewed. You can play with changing any other properties and checking how these changes affect your source files.

  2. Marc Schumacher says:

    Cool feature, but where do I find the full list of supported properties for IntelliJ?
    Best, Schumi

    • Anna Gasparyan says:

      When you right-click a folder and select New | EditorConfig File, check the IntelliJ IDEA-specific checkbox in the dialog that opens and, if needed, select the languages used in your project. An .editorconfig file will be generated with all IntelliJ-specific properties listed as comments

  3. phil swenson says:

    I would love to see a .project-config, .run-config files in addition to this…. the xml .idea files are inscrutable and very hard to automate/share. and throw in a .keybindings file too while you’re at it 😉

    currently setting up idea projects is painful and manual… no one shares the configs, it’s re-create manually for everyone. I know some check in the .idea folder but few do.

    jetbrians could start the equivalent for .editorconfig for other types of functions!

  4. I really like gutter icons which indicate that some section is overriding/being overridden by another section.

    For example, some settings in [Java] section are overriding others in [*].

    However, it looks like it now works just in the same .editorconfig file. It would be a lot more useful if it could detect overrides across the whole config file hierarchy.

    For example, a nested editor config file a few levels deep would show it is overriding some settings from the root editor config file etc.

    It would be a cool extension to the current feature. Is this planned for the final release or is it something you would consider implementing? Thanks a lot.

  5. Andrei says:

    When will this be available on other intelliJ-based ide’s? For example on Android Studio, App Code and etc.

  6. Asaf Mesika says:

    Is there a way to export existing project code formatting as editorconfig file so all developer using the same project share it?

Leave a Reply

Your email address will not be published. Required fields are marked *