microsoftgraph / microsoftgraph/msgraph-metadata
OpenAPI definition contains paths for non-existing endpoints (breaking changes)
Nobody has claimed this yet.
- Dominant language
- XSLT
- Stars
- 166
- Forks
- 55
- Avg merge
- 16h 12m
- Merged PRs (30d)
- 14
Description
OpenAPI document defines paths which contain .../tables/{workbookTable-id}/rows/{workbookTableRow-id}
When calling the endpoint either directly or from any client it returns BadRequest with error code ApiNotFound.
It's definitely a breaking change. For now, workaround is to use .../rows/itemAt(index={index}).
It makes live harder for developers if OpenAPI document defines non-existing endpoints.
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 the OpenAPI definition and locate the paths containing tables/{workbookTable-id}/rows/{workbookTableRow-id}. Confirm they return BadRequest with ApiNotFound, compare them with the rows/itemAt(index={index}) workaround, and ensure the published definition no longer exposes non-existing endpoints.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- openapi
- Domain
- api
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100