Open atomfrede opened 4 years ago
I think it should be handled here, by the jooq blueprint. IMO we should add new configuration parameters in main generator to indicate the server side language and framework used by the generator project (java/spring, java/quarkus, java/micronaut, kotlin/spring, ...) and ease a blueprint such as jooq one to decide if it's compatible with server technologies.
I'll be watching this project and will reply to any strictly jOOQ-related questions. From my experience with this third party contribution here: https://github.com/etiennestuder/gradle-jooq-plugin, maybe 30% - 50% of all questions might be strictly jOOQ-related
I think it should be handled here, by the jooq blueprint. IMO we should add new configuration parameters in main generator to indicate the server side language and framework used by the generator project (java/spring, java/quarkus, java/micronaut, kotlin/spring, ...) and ease a blueprint such as jooq one to decide if it's compatible with server technologies.
Agreed.
This is more a general question. Which project would be responsible to provide support for the micronaut blueprint? Should/must/can do it this blueprint or the micronaut blueprint (if detecting this blueprint)?