Consider propagating some of the default configurations done on the schema module down to sub-modules whenever possible.

[StylianosGakis]

Use case

In my schema module, I had generateOptionalOperationVariables.set(false) and I was initially quite confused why my code generated did not follow this configuration setting. codegenModels gets propagated down to child modules properly so I had made the assumption this would apply here too, hence my initial confusion

Describe the solution you'd like

Consider, if possible, propagating down more such settings made to the schema module down to the sub modules as the default value, and of course let them opt-out for individual settings if it should be possible.

[BoD]

The ideal solution here would be to have a dedicated DSL to differentiate schema and feature modules. This would imply a lot of breaking changes probably so it's not in the immediate future.

[StylianosGakis]

Even since back then, I can't say I've encountered this as a problem again. Probably since these things are not things we change too often. Just thought I'd mention to note that this is not the most urgent thing in the world for sure.