microsoftgraph / microsoftgraph/msgraph-metadata
Invalid http code 2XX, should be 200, 201, etc
Open
Nobody has claimed this yet.
ToTriage
- Dominant language
- XSLT
- Stars
- 166
- Forks
- 55
- Avg merge
- 16h 12m
- Merged PRs (30d)
- 14
Description
There are 100s of operations declaring 2XX as HTTP response code. The value 2XX is not a valid HTTP code. It must be actual number.
Ref:
- https://swagger.io/specification/#patterned-fields-1
- https://swagger.io/docs/specification/v3_0/describing-responses/#:~:text=Media%20Types.-,HTTP%20Status%20Codes,-Under%20responses%2C%20each
38 items:
39 type: string
40 responses:
41 2XX:
42 description: Retrieved entity
43 content:
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
Start with openapi/v1.0/openapi.yaml and inspect the response declarations, including the examples at the reported paths. Replace invalid 2XX response keys with actual HTTP status codes, then validate the OpenAPI metadata against the linked specification references; done means no response declaration uses 2XX.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- openapi
- Domain
- api
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100