Skip to content

[ALL-GENS] - Feature - Remove vendor extensions from operations and schemas; Add vendor extensions to operations and schemas without touching open api spec#22992

Draft
Picazsoo wants to merge 3 commits intoOpenAPITools:masterfrom
Picazsoo:feature/sideload-vendor-extensions
Draft

[ALL-GENS] - Feature - Remove vendor extensions from operations and schemas; Add vendor extensions to operations and schemas without touching open api spec#22992
Picazsoo wants to merge 3 commits intoOpenAPITools:masterfrom
Picazsoo:feature/sideload-vendor-extensions

Conversation

@Picazsoo
Copy link
Contributor

@Picazsoo Picazsoo commented Feb 17, 2026

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

Enable sideloading of OpenAPI vendor extensions for models and operations, so generators can add or remove extensions (e.g., x-kotlin-implements) via configuration without editing the source spec. This helps align outputs across generators and simplifies customization.

  • New Features

    • New config keys: modelVendorExtensionAdd/remove and operationVendorExtensionAdd/remove (in additionalProperties).
    • Models: support class-level ("class") and field-level ("fields") add/remove; added values are merged with existing ones.
    • Operations: support method-level ("method") and parameter-level ("parameters"/"params") add/remove; added values are merged.
  • Refactors

    • Consolidated Kotlin Spring server tests and removed a duplicate test file.
    • Added tests for adding/removing x-kotlin-implements and a new spec (petstore-without-x-kotlin-implements.yaml).
    • Kept gradle wrapper generation tests in the updated suite.

Written for commit 37e142e. Summary will update on new commits.

@Picazsoo Picazsoo changed the title [ALL-GENS] - Feature - sideload operations and schema vendor extensions / remove operations and schema vendor extension [ALL-GENS] - Feature - Remove vendor extensions from operations and schemas; Add vendor extensions to operations and schemas without touching open api spec Feb 17, 2026
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.

1 participant