We use Lombok sparingly in our own implementation details; we try to avoid abusing it for publicly visible code (configured classes).
@EqualsAndHashCodeare mostly fine
@Settershould be avoided in classes which are not plain stupid POJOs
@SneakyThrowsshould be avoided in best effort
YAML & Magnolia definitions
YAML is a highly-prominent part of Magnolia configuration; we recommend the following throughout YAML definitions:
- Put the
fieldType) before any other specific property
- except for names within sequences
- Indent sequence values (so they don't appear to be on same level as their parent)
class: info.magnolia.foo.MySmartDefinition components: - name: First component class: info.magnolia.foo.MySmartComponent description: Some short description of the first component - name: Second ...