Skip to content

Add defaultToEmptyContainer option to java generators#22869

Merged
wing328 merged 1 commit intomasterfrom
option-defaultToEmptyContainer
Feb 1, 2026
Merged

Add defaultToEmptyContainer option to java generators#22869
wing328 merged 1 commit intomasterfrom
option-defaultToEmptyContainer

Conversation

@wing328
Copy link
Copy Markdown
Member

@wing328 wing328 commented Feb 1, 2026

to close #21505

PR checklist

  • Read the contribution guidelines.
  • Pull Request title clearly describes the work in the pull request and Pull Request description provides details about how to validate the work. Missing information here may result in delayed response from the community.
  • Run the following to build the project and update samples:
    ./mvnw clean package || exit
    ./bin/generate-samples.sh ./bin/configs/*.yaml || exit
    ./bin/utils/export_docs_generators.sh || exit
    
    (For Windows users, please run the script in WSL)
    Commit all changed files.
    This is important, as CI jobs will verify all generator outputs of your HEAD commit as it would merge with master.
    These must match the expectations made by your contribution.
    You may regenerate an individual generator by passing the relevant config(s) as an argument to the script, for example ./bin/generate-samples.sh bin/configs/java*.
    IMPORTANT: Do NOT purge/delete any folders/files (e.g. tests) when regenerating the samples as manually written tests may be removed.
  • File the PR against the correct branch: master (upcoming 7.x.0 minor release - breaking changes with fallbacks), 8.0.x (breaking changes without fallbacks)
  • If your PR solves a reported issue, reference it using GitHub's linking syntax (e.g., having "fixes #123" present in the PR description)
  • If your PR is targeting a particular programming language, @mention the technical committee members, so they are more likely to review the pull request.

Summary by cubic

Adds a defaultToEmptyContainer option to Java-based generators. When enabled, container fields default to empty collections instead of null.

  • New Features

    • Added CLI/config option defaultToEmptyContainer in AbstractJavaCodegen and updated docs across Java and Groovy generators.
    • Reduces null checks in generated code and makes iteration/collection operations safer.
  • Migration

    • Set additionalProperties defaultToEmptyContainer=true (or config option) when generating code.

Written for commit 7d73a4c. Summary will update on new commits.

@wing328 wing328 marked this pull request as ready for review February 1, 2026 16:21
@wing328 wing328 added this to the 7.20.0 milestone Feb 1, 2026
Copy link
Copy Markdown
Contributor

@cubic-dev-ai cubic-dev-ai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No issues found across 28 files

@wing328 wing328 merged commit 7506b6c into master Feb 1, 2026
15 checks passed
@wing328 wing328 deleted the option-defaultToEmptyContainer branch February 1, 2026 16:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[BUG] defaultToEmptyContainer not working with Maven plugin

1 participant