Skip to content

Remove lombok from dependencies #25

@Sporiff

Description

@Sporiff

I've been using Lombok to reduce some boilerplate, but I'm finding that it reduces readability somewhat and feels a bit like dark magic. Spring already uses enough annotations as it is.

Since Eclipse and IntelliJ can both easily handle generating most of this boilerplate, we should remove Lombok to avoid annotation collisions and to keep code more readable (even if it's more verbose). Verbosity is not an impediment to performance.

Metadata

Metadata

Assignees

Labels

Type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions