lombok-intellij-plugin: Support for Records in Java - false compilation error reported

Short description

Incorrect compilation issue reported by the plugin while using the records.

Since the latest version of IntelliJ, the IDE has started supporting Records in Java introduced as a preview feature in Java-14.

Expected behavior

There should be no compile error reported by the plugin based on the .class generated.

Version information

IDEA Version: IntelliJ IDEA 2020.1 EAP (Community Edition) Build #IC-201.6487.11, built on March 18, 2020 Runtime version: 11.0.6+8-b765.15 x86_64 macOS 10.14.6

Plugin Version: 0.29-EAP

Steps to reproduce

Create a record type as follows

@lombok.AllArgsConstructor public record Java(String version) { }

Create an instance of this class using the appropriate constructor and observe the behavior.

System.out.println(new Java("14").version());

The plugin highlights the “Cannot resolve constructor” message, on the other hand, the code compiles and executes correctly on the IDE.

Sample project

I have reported a reproducible issue on Stackoverflow with the observation and behavior with and without the plugin installed in the IDE.

I am able to reproduce this error on the sample project by following the steps described above

Additional information

In general, seems like Lombok in itself needs to support Records as well - https://github.com/rzwitserloot/lombok/issues/2356

About this issue

Original URL
State: open
Created 4 years ago
Reactions: 7
Comments: 18 (2 by maintainers)

Most upvoted comments

Same issue here. We’re using @Builder on records, but IntelliJ doesn’t recognise them properly.

This doesn’t work:

@Builder
public record MyRecord(String myField) {}

This does:

public record MyRecord(String myField) {
    @Builder public MyRecord {}
}

Both scenarios work when compiling from the command-line with Maven.

So, it’s pretty easy to work around, but we’re using Lombok to get rid of boilerplate, not introduce more of it 😉

jqno on Nov 2, 2021

@Builder support would be very helpful 😃 https://youtrack.jetbrains.com/issue/IDEA-266513

marx-freedom on Jul 11, 2021

Hi, it seems that Lombok supports Java 16 records https://github.com/projectlombok/lombok/issues/2356, any update?

UkonnRa on May 19, 2021

Unable to reproduce this issue, this issue should be closed and marked as fixed.

linghengqian on Sep 12, 2022

What’s the purpose of the @AllArgsConstructor annotation? Records already have such a constructor.

Are you hoping Lombok will just ignore the annotation in this case?

I’m not sure how useful the @AllArgsConstructor annotation is on a record - in my case it’s the @Builder i’d like 😃

EliasJorgensen on Jun 18, 2021

Same thing here… this is the only thing stopping me to update my projects to Java 17 LTS.

intellitour on Nov 4, 2021

Workaround does not seem to work when @Builder is used together with @With.
Here @With works, but not @Builder:

@With
@Builder
record Test (int e) {
    Test {}
}

Here @Builder works, but not @With:

@With
record Test (int e) {
    @Builder
    Test {}
}

hajdamak on Nov 24, 2021

@mplushnikov Any update on this? This is currently the only block for us to adopt using Records in our projects. Lombok support for Records was added in v1.18.20, so it should be possible to implement 😄 Thanks!

EliasJorgensen on Jun 13, 2021

@hajdamak Brilliant! Thank you, the builder finally works. I wasn’t even aware that @With exists.

MCakrt on Nov 25, 2021

What’s the purpose of the @AllArgsConstructor annotation? Records already have such a constructor. Are you hoping Lombok will just ignore the annotation in this case?

I’m not sure how useful the @AllArgsConstructor annotation is on a record - in my case it’s the @Builder i’d like smiley

Then I’d suggest using @With

dstibbe on Sep 9, 2021