OpenAPI schema for Content create operation is wrong
Open
Nobody has claimed this yet.
Issue
- Dominant language
- Python
- Stars
- 598
- Forks
- 168
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 86
Description
The OpenAPI schema for Content create operation causes the generated client to have a signature that looks like this:
def create(self, relative_path, **kwargs): # noqa: E501
"""Create a file content # noqa: E501
All other create operations have a signature like this:
def create(self, file_file_remote, **kwargs): # noqa: E501
"""Create a file remote # noqa: E501
Contributor guide
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
Inspect the OpenAPI schema for the Content create operation and compare it with the schemas for the other create operations shown in the issue. Regenerate or inspect the client to confirm the Content method uses the expected parameter name, then verify that the generated signature matches the other create methods.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- openapi, python
- Domain
- api
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100