Context:

- Weak entity code handling. - Difficulty in maintaining current classes during functionality implementation.

Decision:

- Lombok can only be used in the client view layer. - Services and repositories will utilize Java Records.

Pros:

• Improved readability.
• Enhanced maintainability.
• Core domain remains clean.

Cons:

• Additional dependency.
• [object Object]
• [object Object]

Status: Accepted -> In use -> Update (Reason: migrate to newer JDK, use records in repo layers)

---