Skip to content

[BUG] operationIdNameMappings in openapi-generator-maven-plugin do not work #21224

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
6 tasks
anadal-fundaciobit opened this issue May 5, 2025 · 0 comments
Open
6 tasks

Comments

@anadal-fundaciobit
Copy link

Bug Report Checklist

  • Have you provided a full/minimal spec to reproduce the issue?
  • Have you validated the input using an OpenAPI validator (example)?
  • Have you tested with the latest master to confirm the issue still exists?
  • Have you searched for related issues/PRs?
  • What's the actual output vs expected output?
  • [Optional] Sponsorship to speed up the bug fix or feature request (example)
Description

operationIdNameMappings in openapi-generator-maven-plugin do not replace operationIDs

openapi-generator version

7.13.0

OpenAPI declaration file content or url

openapi_signature_v1.json

Generation Details

getDocumentaryTypes is generated as getDocumentaryTypesOnServer and getDocumentaryTypesDirectOnWeb, and it should be "getDocumentaryTypes" in both cases

Steps to reproduce

Create a same method in two services with two operationID. You add operationIdNameMappings in openapi-generator-maven-plugin to generate the service client with same name. The methods names generated in the client are the originals, and it should be the defined one in operationIdNameMappings

Related issues/PRs
Suggest a fix
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant