OpenAPITools / OpenAPITools/openapi-generator

[BUG] List of missing or broken APIs moving from swagger-codegen to openapi-generator

Open
#4,662 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Issue: Bug
Dominant language
Java
Stars
26.8k
Forks
7.7k
PR merge metrics
PR metrics pending

Description

Bug Report Checklist
  • What's the version of OpenAPI Generator used?
  • Have you search for related issues/PRs?
Description

I'm transitioning from swagger-codegen to openapi-generator and some errors are being thrown after updating my gradle.build file.

  • Subclasses of DefaultCodegen(), CodegenConfig can't override
    • preprocessSwagger(swagger:)
    • getSwaggerType(property:)
    • getTypeDeclaration(property:)
    • postProcessOperations(objs:)
    • addAdditionPropertiesToCodeGenModel(codegenModel:, swaggerModel:)
    • fromModel(name: String, model: Model, allDefinitions: MutableMap<String, Model>?): CodegenModel
    • fromOperation(path: String?, httpMethod: String?, operation: Operation?, definitions: MutableMap<String, Model>?, swagger: Swagger?): CodegenOperation
    • no versions of getTypeDeclaration() accepts Property types

because those functions don't exist on supertypes.

  • Missing or private properties on CodegenConfigurator
val configurator = CodegenConfigurator()
configurator.lang = lang // missing
configurator.inputSpec = parsed['i'] // private
configurator.outputDir = parsed['o'] // missing
openapi-generator version

4.2.1

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the Gradle-based migration with openapi-generator 4.2.1, then inspect DefaultCodegen, CodegenConfig, and CodegenConfigurator for the listed missing overrides and properties. Compare the affected APIs with the reported swagger-codegen usage; done means each incompatibility is verified and either addressed or clearly documented.

Written by the indexing model from the issue text.

Assessment

Tech stack
java, kotlin
Domain
api, tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.