Meet Grazie: the ultimate spelling, grammar, and style checker for IntelliJ IDEA
Development is not all about programming languages. A lot of text in your code is for humans, not the compiler: string literals, comments, Javadocs, commit messages, and much more requires at least some knowledge of English or other natural languages, depending on your team and users. So isn't it great when your IDE checks not only your code constructs, but also the spelling, grammar, and style of natural language text? Now we have a great tool to reduce your need for native-speaker editors, or at least reduce the number of mistakes that they need to clean up in your code. Grazie is a plugi
IntelliJ IDEA 2019.2.4 is out!
IntelliJ IDEA 2019.2.4, an important bug-fix update is now available! This minor release adds the option to choose how a compiler will treat a dedicated annotation processor path: as an ordinary classpath or as a module-path containing annotation processor classes packaged into JPMS-aware jars. For the module-path option, go to File | Settings | Build, Execution, Deployment | Compiler | Annotation Processors, specify the processor path, and select Use --processor-module-path compiler option (for Java 9 and later): (more…)
Refactoring: Inline Method in IntelliJ IDEA
The idea of Inline Method Refactoring is simple – replace a method call with its contents. Still, it is really powerful. But to appreciate its power, you need to know its use cases. Let’s understand why, when, and how to apply the Inline Method refactoring and how IntelliJ IDEA can help you get started. (more…)
IntelliJ IDEA 2019.2 EAP3: Code Style per Scope, Refreshed Code Completion Popup, and More
This week’s EAP build for the upcoming IntelliJ IDEA 2019.2 is ready for you to download and try all the new things in action. Manage code style per scope via EditorConfig The upcoming IntelliJ IDEA 2019.2 will bring a highly anticipated feature – the ability to manage all code style settings for each scope individually. To set the code style settings for the selected scope, simply place the EditorConfig file in the root directory of a module or package. You can have as many EditorConfig files as you need in a single project. For instance, you will be able to specify different code st