Add support for a la carte derivation about derive4j HOT 5 CLOSED

👍 to

a more generic (disable set, disable mod, disable get) generation control

from derive4j.

I can add an enum
Derivation = Getters | Setters | FluentPatternMatching
and a new attribute Derivation[] omit() default {} to @Data
Also moving all public static methods at the top of the generated file could help get important stuff under the 2500 lines threshold of Idea.
@talios, WDYT?

from derive4j.

Derivation sounds good. as does moving the static methods to the top.

Would it be worth considering genererating the setters/mods/matching into separate classes as well? Having the single class is nice, but may not scale?

Ideally one should probably not have this amount of cases in a single set of cases tho, which is one of the reasons I was looking at switching to derive4j in for this piece of code ( aside from jADT being unmaintained ).

Since we're starting to get a lot of commands/cases in this piece of code ( essentially an immutable set of events in a CQRS style system, but much more minimal ) we're wanting to look at breaking them into smaller set's of cases with a common super interface which dervie4j's syntax offers quite nicely.

from derive4j.

@talios
I'm going to add the following annotation property in @Derive:

public @interface Derive {
  // ...
  Make[] make() default { lambdaVisitor, constructors, getters, modifiers,
                          lazyConstructor, patternMatching, catamorphism };
  // ...
}

So that one can override the default and make derive4j only generate what is explicitly defined.
Is that ok for you?
(Derive4j will take care of dependencies. ie if you specify only modifiers then constructors will be automatically generated as well even if not mentioned explicitly)

from derive4j.

+10 that looks good to me.

from derive4j.