Setting an optional value should not require wrapping in "Optional"

[koppor]

At 62011fe#diff-9894c8ca988dd9ba18c16d1cc0176ca25e915f1b212f12e9c5f285d44fa10e72R81, the value of the example optional Property "b" was made using .b(Optional.of("bbbb"). I wonder, why one could not simply write .b("bbbb")? The method b can create the Optional by itself. - IMHO the code would be more readable.

• Refs Alternate staged builders that handle optional, etc. #180 (where the feature was introduced)
• Refs Release of staged builders #183 (asking for a release; IMHO the syntax should be thought of again before a release)

[Randgalt]

You can get that behavior by using addConcreteSettersForOptional = true. E.g.,

@RecordBuilder
@RecordBuilder.Options(builderMode = RecordBuilder.BuilderMode.STAGED_REQUIRED_ONLY, interpretNotNulls = true, useImmutableCollections = true, addConcreteSettersForOptional = true)
public record OptionalListStaged(int a, Optional<String> b, double c, List<Instant> d, @Null String e, String f) {
}

[koppor]

Thank you for the quick reply! 🤩 (I was about to comment after reading through https://github.com/Randgalt/record-builder/blob/master/options.md)