When trying to integrate this plugin with an internal plugin, we ran into a limitation caused by the name field not being public. We are trying to use the JooqConfig class in a new context, and not being able to access the name means we cannot implement "map jooq config name to java config name" logic in our internal plugin.
This commit adds a getter for the field to support such a use case.
When trying to integrate this plugin with an internal plugin, we ran into a limitation caused by the name field not being public. We are trying to use the
JooqConfigclass in a new context, and not being able to access the name means we cannot implement "map jooq config name to java config name" logic in our internal plugin.This commit adds a getter for the field to support such a use case.