Add customizeSettings to JavaCodegenIntegration#1264
Merged
Conversation
This allows integrations to customize things like default settings and default plugins before interceptors() run. Closes #1212
sugmanue
approved these changes
Jun 24, 2026
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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 allows integrations to customize things like default settings and default plugins before interceptors() run.
Closes #1212
What behavior changes?
Describe the observable difference in behavior before and after this change.
This change makes it so you customize the settings of the generator before codegen begins.
Why is this change needed?
Explain the motivation: bug, feature request, refactor, performance, etc.
We previously did not have a reliable way to add default settings or default plugins during codegen using a codegen integration. See #1212. It also exposed a latent bug in how we were ignoring the addition of adding the AWS credential chain by default when AWS traits are detected.
How was this validated?
List tests added, benchmarks run, or manual verification performed.
Added unit tests
What should reviewers focus on?
Point reviewers to the files or sections that contain the interesting logic.
Additional Links
Related issues, design docs, or prior art.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.