having an empty generate object available that can be customized in the generator about jooq-plugin

[adrianskrobaczrevolut]

Ow, I see I confused the Generator with Generate 😅 Now I get you and it makes a lot of sense 👍 I'll add it next release and keep you updated here 🙂

[encodeering]

@adrianskrobaczrevolut very cool, just updated the version and it works great

[adrianskrobaczrevolut]

Hello @encodeering 🙂
Sorry for late response. May I ask what is your use case 🙂 ? I'm asking because the generator passed to the lambda is already preconfigured(you may still modify it as you please), but cannot imagine why you would need to build it from scratch 🤔

[encodeering]

Hi @adrianskrobaczrevolut,

we are running version 0.3.2 and need to change a property for jooq that is part of the Generate () context, as a default has changed when migrating jooq from 3.12 to 3.13.

The second code snippet is what we are currently doing and I was wondering whether it would make sense to create an empty Generate () instance somewhere in the method starting on L179, as we are seeing a NPE otherwise.

Like

Generator()
    .withGenerate(Generate())
    .withName(JavaGenerator::class.qualifiedName)
    ...

to customize it with

        customizeGenerator {
            generate.withXXX ()
            database.withXXX ()
        }

Cheers

[adrianskrobaczrevolut]

@encodeering added in the latest release 0.3.4 🙂