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
  • !12146

Adds not to CodegenComposedSchemas and uses it in python-experimental

  • Review changes

  • Download
  • Email patches
  • Plain diff
Merged Administrator requested to merge github/fork/spacether/feat_adds_not into master Apr 15, 2022
  • Overview 0
  • Commits 1
  • Pipelines 0
  • Changes 189

Created by: spacether

Adds not to CodegenComposedSchemas and uses it in python-experimental Note: for the AnyTypeNotString component schema that I made, even though it has not defined, swagger-parser parses it as a Schema rather than a ComposedSchema instance, so I needed to add code checking if not was present when setting composed schema data in the Java layer.

The not feature is used in python-epxerimental in: modules/openapi-generator/src/main/resources/python-experimental/schemas.handlebars and a verification test was added in test_AnyTypeNotString.

This PR also adds composition keywords to SchemaSupportFeatures so users can better tell if a keyword is supported.

  • allOf
  • anyOf
  • oneOf
  • not

Multiple people are confused about what our tooling supports so adding these keywords as supported schema features will help them:

  • https://openapi-generator.slack.com/archives/CLSB0U0R5/p1639692005303100
  • https://openapi-generator.slack.com/archives/CLSB0U0R5/p1641649832018400
  • https://openapi-generator.slack.com/archives/CLSB0U0R5/p1625069243283300
  • https://openapi-generator.slack.com/archives/CLSB0U0R5/p1631618123117700
  • https://github.com/OpenAPITools/openapi-generator/issues/503
  • https://github.com/OpenAPITools/openapi-generator/issues?page=1&q=is%3Aissue+is%3Aopen+oneOf+in%3A+title

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.
Assignee
Assign to
Reviewers
Request review from
Time tracking
Source branch: github/fork/spacether/feat_adds_not