with one click
code-style
Code style rules for IntelliJ codebase. Use when writing or reviewing code for style compliance.
Menu
Code style rules for IntelliJ codebase. Use when writing or reviewing code for style compliance.
| name | code-style |
| description | Code style rules for IntelliJ codebase. Use when writing or reviewing code for style compliance. |
Follow the IntelliJ Coding Guidelines with these IntelliJ-specific rules.
@ApiStatus.Experimentalcommunity/platform/build-scripts/kotlin-style-recommendations.md for build-scripts code:
@JvmField for internal data class fields.put()/.get() instead of [] operatorHashMap/HashSet/LinkedHashMap instead of mutableMapOf()/mutableSetOf()/rustrover directory you must always use standard Kotlin formatting rules with 4 spaces indentation.Comprehensive testing reference for running tests in IntelliJ codebase via tests.cmd. Use when running, debugging, or troubleshooting test execution.
Guidelines for implementing IntelliJ actions (AnAction). Use those rules when you need to create or change an action in the intellij platform.
Comprehensive testing reference for running tests in IntelliJ codebase via tests.cmd. Use when running, debugging, or troubleshooting test execution.
Guidelines for implementing IntelliJ actions (AnAction). Use those rules when you need to create or change an action in the intellij platform.
Pluginize a Product DSL module set by hand-writing a wrapper plugin module next to its feature modules. Use when promoting modules out of an aggregate module set (e.g. `essential`, `ide.common`) into a bundled plugin so products can include or omit them through normal plugin wiring, when updating bundled plugin registration for such a wrapper, or when fixing tests whose plugin loading logs show a missing wrapper plugin for a former module set.
Pluginize a Product DSL module set by hand-writing a wrapper plugin module next to its feature modules. Use when promoting modules out of an aggregate module set (e.g. `essential`, `ide.common`) into a bundled plugin so products can include or omit them through normal plugin wiring, when updating bundled plugin registration for such a wrapper, or when fixing tests whose plugin loading logs show a missing wrapper plugin for a former module set.