indeedeng / indeedeng/iwf-python-sdk
Possible missing pieces from generated code
Open
Nobody has claimed this yet.
low-priority
won't fix
- Dominant language
- Python
- Stars
- 6
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
When updating the IDL:
➜ iwf-python-sdk git:(main) ✗ poetry run openapi-python-client update --path iwf-idl/iwf-sdk.yaml --config .openapi-python-client-config.yaml
Updating iwf_api
Warning(s) encountered while generating. Client was generated, but some pieces may be missing
WARNING parsing POST /api/v1/workflow/getWithWait within default.
Invalid response status code 420 (not a valid HTTP status code), response will be ommitted from generated client
WARNING parsing POST /api/v1/workflow/rpc within default.
Invalid response status code 420 (not a valid HTTP status code), response will be ommitted from generated client
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the generation command using iwf-idl/iwf-sdk.yaml and .openapi-python-client-config.yaml, then inspect the generated iwf_api client for POST /api/v1/workflow/getWithWait and POST /api/v1/workflow/rpc. Determine how the generator should represent the 420 responses and verify that regeneration no longer omits those response pieces or emits the warnings.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- openapi, python
- Domain
- api, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100