Failed validating 'oneOf'
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- python
- Domain
- backend-api-design
Research direction
No files, tests, or entry points are named. Start by reproducing the supplied validation error with the OpenAPI instance, then trace validation of the callbacks property and its oneOf schemas. Done means identifying whether the reported structure is invalid or the validator is producing an incorrect diagnostic, with a focused regression test if a defect is confirmed.
Written by the indexing model from the issue text.
Description
Hello,
I don't understand the following validation error:
{'{$response.header.Location}': {'get': {'requestBody': {}, 'responses': {'301': {'x-scope': ['', '#/components/callbacks/moveProgress'], '$ref': '#/components/responses/MoveProgress'}, '303': {'x-scope': ['', '#/components/callbacks/moveProgress'], '$ref': '#/components/responses/MoveSuccess'}}}}} is not valid under any of the given schemas
Failed validating 'oneOf' in schema['properties']['paths']['patternProperties']['^/']['properties']['put']['properties']['callbacks']['additionalProperties']:
{'oneOf': [{'$ref': '#/definitions/callback'},
{'$ref': '#/definitions/reference'}]}
On instance['paths']['/users/user/{dn}']['put']['callbacks']['move-progress']:
{'{$response.header.Location}': {'get': {'requestBody': {},
'responses': {'301': {'$ref': '#/components/responses/MoveProgress',
'x-scope': ['',
'#/components/callbacks/moveProgress']},
'303': {'$ref': '#/components/responses/MoveSuccess',
'x-scope': ['',
'#/components/callbacks/moveProgress']}}}}}
The x-scope was not added by myself. I don't have any oneOf defined.
Maybe someone can point me to the error?
- Dominant language
- Python
- Stars
- 409
- Forks
- 73
- PR merge metrics
- No merged PRs in 30d
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.
More from python-openapi/openapi-spec-validator
-
Difficulty 4/5 3-5 days Newbie friendliness 55/100
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
-
Difficulty 3/5 1-2 days Newbie friendliness 30/100
-
Difficulty 4/5 3-5 days Newbie friendliness 42/100
python-openapi/openapi-spec-validator#400 · 1 comment ·
-
kind/bug/confirmed
Difficulty 5/5 Over a week Newbie friendliness 25/100
python-openapi/openapi-spec-validator#373 · 1 comment ·
All issues in python-openapi/openapi-spec-validator
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
learningequality/ricecooker#747 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
BSData/horus-heresy-3rd-edition#3171 ·
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
run-llama/llama_index#23199 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
KhronosGroup/glTF-Blender-IO#2769 ·