feat(configuration): allow to configure the generated visibility modifier #51
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jcornaz
changed the title
We are quite strongly coupled to jOOQ in this project by design. I don't really see a huge chance that we'd want to deviate from whatever Lukas will use in jOOQ, so I'd be fine with your current implementation. |
ursjoss
approved these changes
Sep 5, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This adds the ability to configure which visibility modifier the generated code should have.
See: https://www.jooq.org/doc/3.15/manual/code-generation/codegen-advanced/codegen-config-generate/codegen-generate-visibility-modifier/
@ursjoss, I'm not sure about adding
org.jooq.meta.jaxb.VisibilityModifierinto the public API. It is convenient because it already exists, but I wonder if I should hide it behind our own enum. What do you think?