microsoftgraph / microsoftgraph/msgraph-metadata
Unused or Orphaned components in `openapi.yaml`
Nobody has claimed this yet.
- Dominant language
- XSLT
- Stars
- 166
- Forks
- 55
- Avg merge
- 16h 12m
- Merged PRs (30d)
- 14
Description
There are 100s of unused or orphaned component definitions found in openapi.yaml. It’s good contract hygiene to prune anything that isn’t used, out of it.
Here are some of the examples of those unused component definitions and their line numbers.
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 example component definitions at the cited line numbers. Determine which component definitions are not referenced elsewhere in the contract, then remove the unused entries while preserving all referenced components; the issue is done when the orphaned definitions have been pruned without breaking the OpenAPI document.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- openapi
- Domain
- api
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100