Redocly / Redocly/openapi-starter
Ideas for planned updates
Open
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 220
- Forks
- 133
- PR merge metrics
- No merged PRs in 30d
Description
Some additional examples and updates to consider (make each one into an issue before you start working on it)
- callback
- examples for content type x-www-form-encoded and octet-stream
- #131
- XML schemas
- #130
- better response examples
(original list from #7)
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
No file, test, or entry point is named. Start by reviewing the checklist in issue #125 and the referenced issues #131, #130, and #7; done means each proposed update has its own clearly scoped issue before implementation begins.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- openapi
- Domain
- api, documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100