Create builder with mandatory fields.

[ololoshka]

Create builder with mandatory fields. Without builder you can make

certain fields be mandatory initiated using constructor only. 

Current builder doesn't provide initialization validation but it can be created.

Here I attach ugly first solution that came on my mind:

https://gist.github.com/isicju/77987f16f55d056d1e0f4a1de7ebf491

In this example you are obliged to initialize user name and user age when

you build it. Otherwise you just can't call builder method. 

I believe that such builder will increase code quality. 

Thanks and best regards. 

[Jan Materne]

Wouldnt it be better to combine builder with javax.validation annotations? And I havent tested if Lombok supports that already ... maybe via config file and copyableannotations ...

Jan

--
You received this message because you are subscribed to the Google Groups "Project Lombok" group.
To unsubscribe from this group and stop receiving emails from it, send an email to project-lombo...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/project-lombok/9773c0b5-0e56-443e-9b91-072572e4db5fn%40googlegroups.com.

[ololoshka]

Javax annotation is trash in general. But even lombok would support it they wont be compile time safe. 

вторник, 7 декабря 2021 г. в 06:28:49 UTC, Jan:

[Michael Berry]

This has come up quite a bit in the past, there's a good wiki page around it: https://github.com/projectlombok/lombok/wiki/FEATURE-IDEA:-%22Mandatory%22-fields-with-@Builder

To view this discussion on the web visit https://groups.google.com/d/msgid/project-lombok/3bf8ccbb-a5ac-4c5b-970e-1b4f8a78cb05n%40googlegroups.com.

--

Thanks,

Michael

[Michael Ernst]

A solution to this problem exists, in the form of a compiler plugin that is compatible with Lombok and that issues a compile-time error if a builder client might fail to set a mandatory field.

The tool is called the Called Methods Checker.  It is distributed as part of the Checker Framework and it has built-in support for Lombok builders.  It does not require you to change your coding style and it does not change the code that Lombok emits.  It does require some programmer-written annotations -- in experiments, about one per 1600 lines of non-comment, non-blank Java code.  The plugin is sound:  if it issues no errors, then your code never fails to supply all mandatory fields.  Like any static analysis tool, it can issue false positive warnings that you suppress with a @SuppressWarnings annotation.  It works best together with the io.freefair.lombok Gradle plugin.

Full disclosure:  I am not the author of the Called Methods Checker, but I did contribute to it.  Please give it a try and submit a bug report if you have any problems.

-Mike

To view this discussion on the web visit https://groups.google.com/d/msgid/project-lombok/CAKSFpK6n7rXA20ifVNCsF76U5aE1W357UkruZPygPTMRU9i83Q%40mail.gmail.com.