oas-apigee-mock: Errors from the OAS Validate Policy not propagated
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 221
- Forks
- 174
- PR merge metrics
- No merged PRs in 30d
Description
When generating a mock proxy (using oas-apigee-mock )that has the OAS Validation policy, the errors that are produced by the policy are not returned in the response, instead it just returns a generic HTTP 400. Ideally, we should be propagating those errors in the response body.
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
Start in the oas-apigee-mock tool and reproduce a mock proxy request that fails OAS validation. Trace how the OAS Validate Policy error becomes the HTTP 400 response, then verify that the response body contains the policy's errors instead of only a generic status.
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
- 42/100