Some API, like the AWS SDK, heavily rely on the builder pattern to create different data structures. Despite all the benefits, this pattern can
become really verbose, especially when dealing with nested structures. In order to reach a more concise code, "Consumer Builders", also called
"Consumer Interface" are often introduced.
The idea is to overload the methods taking others structures in a Builder with a Consumer of Builder instead. This enables to use a lambda instead
of nesting another Builder, resulting in more concise and readable code.
This rule reports an issue when the Consumer Builder methods could be used instead of the classical ones.
Noncompliant code example
SendEmailRequest.builder()
.destination(Destination.builder()
.toAddresses("to-email@domain.com")
.bccAddresses("bcc-email@domain.com")
.build())
.build();
Compliant solution
SendEmailRequest.builder()
.destination(d -> d.toAddresses("to-email@domain.com").bccAddresses("bcc-email@domain.com"))
.build();
