These checks are implemented in the form of a dedicated inspection set, which you can adjust according to your preferences: This is handy because otherwise such an error would not be visible until compile-time, which increases the feedback loop and consequently wastes your time. If there’s a conflict between the annotations, or another Lombok-related problem, IntelliJ IDEA will detect the issue right away. Accessor calls are found just as if the boilerplate was in place: All the essential features, like navigation and rename refactoring, also work well with such code.įor example, we can search for the usages of a backing field whose accessor methods were replaced with Lombok annotations. The same works for ubiquitous loggers, trivial equals() and hashCode() implementations, constructors, and more.īecause IntelliJ IDEA knows the corresponding bytecode will be generated at compilation, the Lombok code is not red. Whenever IntelliJ IDEA recognizes that a member can be replaced with a Lombok annotation, it suggests a quick-fix: There are plenty of trivial accessor methods in our project, so let’s start by replacing them. Now that we’ve made sure that the plugin is enabled and the dependency is on the classpath, let’s look at the features. We can do that either through the build script, or we can just start using Lombok annotations, and IntelliJ IDEA will suggest adding the missing dependency. Now, let’s add Lombok to the project dependencies. Then, make sure that the Lombok plugin is enabled: Let’s start by cloning the canonical spring-petclinic project. Today, let’s explore Lombok support in IntelliJ IDEA and see how they make a project cleaner, less verbose, easier to maintain, and more pleasant to work with. In fact, it’s so highly valued that in the past, when the plugin was not bundled, many users would not upgrade until the plugin was compatible with the newer version of IntelliJ IDEA. IntelliJ IDEA Ultimate comes bundled with the Lombok plugin which makes Lombok even more useful and convenient. What you probably didn’t know is that not only do these 2 technologies work well on their own, but when combined, they’re even more efficient than when used individually If you’re a professional Java developer, you probably use IntelliJ IDEA as your IDE and Lombok as the framework that handles the Java boilerplate.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |