Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Remove Lombok usage in favour of Immutables #336

Open
JaidenAshmore opened this issue Sep 26, 2020 · 1 comment
Open

Remove Lombok usage in favour of Immutables #336

JaidenAshmore opened this issue Sep 26, 2020 · 1 comment
Labels
engineering task A more technically focused task
Milestone
6.0.0

Comments

@JaidenAshmore
Copy link
Owner

Lombok has the disadvantage when developers look at the source files of the library that they get a big warning about the source file not matching the actual code. I am mostly using Lombok for POJOs and builders which can be replaced with Immutables Java which auto generates implementations. Some functionality like @slf4j, @UtilityClass are lost but that is not a big deal at all. Losing @DeleGate sucks but it will just be one conversion effort to replace that.
@JaidenAshmore JaidenAshmore added this to the 4.4.0 milestone Sep 26, 2020
@JaidenAshmore JaidenAshmore added the engineering task A more technically focused task label Sep 26, 2020
@JaidenAshmore JaidenAshmore modified the milestones: 4.4.0, 5.0.0 Oct 4, 2020
@mistriel
Copy link

Totally disagree on that one.
Lombok has the advantage of reducing boiler print code. I'm using IntelliJ along with Lombok plugin and Annotation processing - no warnings what so ever.

@JaidenAshmore JaidenAshmore modified the milestones: 5.0.0, 6.0.0 Jun 18, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
engineering task A more technically focused task
Projects
None yet
Milestone
6.0.0
Development

No branches or pull requests
2 participants
@JaidenAshmore @mistriel