Skip to content
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

control-service: new python client. #1983

Merged
merged 1 commit into from
Apr 27, 2023

Conversation

murphp15
Copy link
Collaborator

Why

The newest python api client is broken and the last working one is very old.

What

In this PR I use the python-nextgen generator instead of the python generator. The behaviour is much more correct and predictable.

There are two bugs in the generated code.
For both these I have created tickets in the openapi generator github project.

I have added string replace workarounds in the gradle step to fix these bugs before we publish the pip package.

next steps(will be tackled in the next few weeks not days): #1982

closes: #1979

How has this been tested?

Locally.
There is actually a draft branch where I import this new version into the cli project and run tests against it to confirm everything is green: #1969

This will always fail in github because 1.0.9 is not released yet till this PR is merged. Then I will open a new PR where I import into cli tool.

Signed-off-by: murphp15 <murphp15@tcd.ie>
@murphp15 murphp15 merged commit f1d3e7e into main Apr 27, 2023
11 checks passed
@murphp15 murphp15 deleted the person/murphp15/release_new_python_client branch April 27, 2023 09:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Python api client release process is broken
4 participants