Add @Singular annotation to all list fields in request dtos

[mjanuszkiewicz-tt]

Allows us to use

builder.property(x)

instead of

builder.properties(new List<>(x))

Technically a breaking change since previously a call to properties overrode the previously set properties, not it's essentially an addAll call. To reset the user would have to call clearProperties. I guess this means if merged we would have to increment a major version.

Soliciting ideas for singular names for

public class ArrivalSearches {
    @NonNull
    List<ManyToOne> manyToOne;
    @NonNull
    List<OneToMany> oneToMany;
}

[Donatas-L]

Tests are failing

[mjanuszkiewicz-tt]

Tests are failing

Fixed, the @Singular annotation means that if we don't add an element we now generate an empty list instead of not outputting a field at all. I will make sure we don't do something weird where missing filed != field with empty list.

[Donatas-L]

How does it work with naming?

@Singular
List<String> withinCountries;

Would be:

builder
.withinCountry("Country 1")
.withinCountry("Country 2")

?

[mjanuszkiewicz-tt]

How does it work with naming?

@Singular
List<String> withinCountries;

Would be:

builder
.withinCountry("Country 1")
.withinCountry("Country 2")

?

Yes. if lombok can't figure out a singular form it won't compile unless you set it manually.

[Donatas-L]

How does it work with naming?

@Singular
List<String> withinCountries;

Would be:

builder
.withinCountry("Country 1")
.withinCountry("Country 2")

?

Yes. if lombok can't figure out a singular form it won't compile unless you set it manually.

So a bit of magical code generation via annotations :D

[mjanuszkiewicz-tt]

So a bit of magical code generation via annotations :D

Yeah, lombok does a lot of heavy lifting for stuff like this.

[danielnaumau]

Can you please update readme and examples?