Bug Report Checklist
Description
After generating a python client for peertube, the tests don't run due to syntax errors:
openapi-generator version
@openapitools/openapi-generator-cli^1.0.10-4.2.3
OpenAPI declaration file content or url
https://framagit.org/LoveIsGrief/PeerTube/blob/44d4ee4fcb7cf8beebac73f85693c09919b91e66/support/doc/api/openapi.yaml
Command line used for generation
It's run in a bash script by a CI that calls the npm package. bash script | npm package (@openapitools/openapi-generator-cli^1.0.10-4.2.3) (line in yarn.lock)
the resulting command should be
npx openapi-generator generate
-i support/doc/api/openapi.yaml
-c "support/openapi/python/def.yaml"
-t "support/openapi/python"
-g "python"
--git-host "framagit"
--git-user-id "peertube-test"
--git-repo-id "apis/python"
-o "dist/api/python"
Steps to reproduce
- Generate python client from peertube api spec
- install virtualenv in output directory
- install
requirements.txt and test-requirements.txt
pytest
Related issues/PRs
#1747 had similar issues but the output was ignored? I'm not entirely sure.
Suggest a fix
Update the template to use the correct fieldnames. They are correctly generated in the model, but not in the test file.
Bug Report Checklist
Description
After generating a python client for peertube, the tests don't run due to syntax errors:
openapi-generator version
@openapitools/openapi-generator-cli^1.0.10-4.2.3
OpenAPI declaration file content or url
https://framagit.org/LoveIsGrief/PeerTube/blob/44d4ee4fcb7cf8beebac73f85693c09919b91e66/support/doc/api/openapi.yaml
Command line used for generation
It's run in a bash script by a CI that calls the npm package. bash script | npm package (@openapitools/openapi-generator-cli^1.0.10-4.2.3) (line in yarn.lock)
the resulting command should be
npx openapi-generator generate
-i support/doc/api/openapi.yaml
-c "support/openapi/python/def.yaml"
-t "support/openapi/python"
-g "python"
--git-host "framagit"
--git-user-id "peertube-test"
--git-repo-id "apis/python"
-o "dist/api/python"
Steps to reproduce
requirements.txtandtest-requirements.txtpytestRelated issues/PRs
#1747 had similar issues but the output was ignored? I'm not entirely sure.
Suggest a fix
Update the template to use the correct fieldnames. They are correctly generated in the model, but not in the test file.