-
-
Notifications
You must be signed in to change notification settings - Fork 6.6k
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
[BUG] ensureUniqueParams not working for typescript-angular client #6032
Labels
Comments
👍 Thanks for opening this issue! The team will review the labels and make any necessary changes. |
I think this should be fixed recently. Please pull the latest master to give it a try |
This was referenced Oct 27, 2023
This was referenced Dec 27, 2023
This was referenced Dec 28, 2023
This was referenced Dec 29, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Bug Report Checklist
Description
When generating a client for a typescript-angular, some function definitions have duplicate argument names despite
ensureUniqueParams
being set totrue
.openapi-generator version
4.3.0. This is my first time using this generator, so I cannot tell if it is a regression.
OpenAPI declaration file content or url
This was observed while generating a client for https://raw.githubusercontent.com/netdata/netdata/master/web/api/netdata-swagger.yaml.
Command line used for generation
openapi-generator generate -i https://raw.githubusercontent.com/netdata/netdata/master/web/api/netdata-swagger.yaml -g typescript-angular -o out -c cfg/swagger-gen-config.json --skip-validate-spec
Note: the
--skip-validate-spec
is needed because there are some missing definitions in the swagger file. Despite this, the client is still successfully generated despite the issue being reported.The contents of
cfg/swagger-gen-config.json
is:Steps to reproduce
out/api/default.service.ts
.4: Search for a function named
badgeSvgGet
ordataGet
. They will have two parameters namedoptions?
. One is from the API definition, the other is for the Angular httpClient options.The expectation is that having the
ensureUniqueParams
flag set will rename one of the generatedoptions?
parameters to something else.Related issues/PRs
I have not found any another issues or PRs.
Suggest a fix
It seems like the generator is not taking the parameters generated for the Angular HttpClient into account when handling the
ensureUniqueParams
logic.The text was updated successfully, but these errors were encountered: