nextcloud / nextcloud/openapi-extractor
Add CI check for openapi-typescript for repos that use it
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- PHP
- Stars
- 11
- Forks
- 4
- Avg merge
- 10h 18m
- Merged PRs (30d)
- 8
Description
Would have caught https://github.com/nextcloud/server/pull/46383 / https://github.com/nextcloud/openapi-extractor/pull/146 earlier.
At least a bit more safety by ensuring openapi-typescript is fine with the generated specification (no definite safety though).
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
No files, tests, or CI entry points are named. Start by locating the repository's CI configuration and the path that generates the OpenAPI specification; done means a CI check validates that specification with openapi-typescript for applicable repositories.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- openapi, php, typescript
- Domain
- api, ci-cd
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100