Skip to content

Remove lombok from dependencies #25

Closed

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.

Activity

  1. added this to the MVP milestone on Nov 26, 2025
  2. self-assigned this
    on Nov 26, 2025
  3. added theissue type on Nov 26, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions