Skip to content
GitLab
Closed
Issue created by Administrator@rootContributor4 of 6 checklist items completed4/6 checklist items

[BUG] [Qt5] Parameterized servers complicated the interface and left unused code

Created by: xconverge

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

This PR added a neat feature:

https://github.com/OpenAPITools/openapi-generator/pull/8183

But made a whole bunch of things useless/nonfunctional...

host, username, port, scheme, basepath, password, apikeys, all now seem to do nothing. You can set them with setters or via the constructor, but the generated code never uses them that I can see.

There is no way to change the host at runtime now, it must be done in the .yml when generating and then selected with the server index PER operation, there is not a way to set an entire api object to use a specific server from the consumer of the client.

That means you MUST know your server information at compile time and cannot change it in anyway after that as a consumer... this seems like an oversight to me unless I am missing something

Related issues/PRs

https://github.com/OpenAPITools/openapi-generator/pull/8183

Suggest a fix

Maybe have the constructor values for these parameters put an entry into the server list (that is set to be index 0 and is the one used) and have a way of easily changing the server index for all operations within the class to use the parameterized server selector separately if desired?