Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • O openapi-generator
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 3,476
    • Issues 3,476
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 402
    • Merge requests 402
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • OpenAPI Tools
  • openapi-generator
  • Merge requests
  • !12237

New option to map inline schema names

  • Review changes

  • Download
  • Email patches
  • Plain diff
Merged William Cheng requested to merge better-inline-naming into master Apr 25, 2022
  • Overview 0
  • Commits 10
  • Pipelines 0
  • Changes 23

New option to map inline schema names, e.g.

java -jar modules/openapi-generator-cli/target/openapi-generator-cli.jar generate -g java -i  modules/openapi-generator/src/test/resources/3_0/inline_model_resolver.yaml -o /tmp/java3/ --skip-validate-spec --inline-schema-name-mappings inline_object_2=SomethingMapped,inline_object_4=nothing_new

Here are what the log looks like:

[main] INFO  o.o.codegen.InlineModelResolver - Inline schema created as inline_object_1. To have complete control of the model name, set the `title` field or use the inlineSchemaNameMapping option.
[main] INFO  o.o.codegen.InlineModelResolver - Inline schema created as inline_response_200. To have complete control of the model name, set the `title` field or use the inlineSchemaNameMapping option.
[main] INFO  o.o.codegen.InlineModelResolver - Inline schema created as inline_response_200_1. To have complete control of the model name, set the `title` field or use the inlineSchemaNameMapping option.
[main] INFO  o.o.codegen.InlineModelResolver - Inline schema created as inline_object_3. To have complete control of the model name, set the `title` field or use the inlineSchemaNameMapping option.
[main] INFO  o.o.codegen.InlineModelResolver - Inline schema created as inline_response_200_2. To have complete control of the model name, set the `title` field or use the inlineSchemaNameMapping option.

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 
    ./bin/generate-samples.sh
    ./bin/utils/export_docs_generators.sh
    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*. For Windows users, please run the script in Git BASH.
  • If your PR is targeting a particular programming language, @mention the technical committee members, so they are more likely to review the pull request.

cc @OpenAPITools/generator-core-team

Assignee
Assign to
Reviewers
Request review from
Time tracking
Source branch: better-inline-naming