openapi-processor / openapi-processor/openapi-parser
split draft implementations
Open
Nobody has claimed this yet.
validator
- Dominant language
- Java
- Stars
- 27
- Forks
- 2
- Avg merge
- 3d 16h
- Merged PRs (30d)
- 8
Description
split the validator into implementations for each single draft instead of a single implementation for all drafts.
- this should make the code easier to maintain
- probably bought by a bit of duplication (?)
- probably adds more complexity when references to other draft versions
- ...
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 locating the validator and how it handles each draft, then clarify the boundaries and cross-draft reference behavior before splitting implementations; done means supported drafts still validate correctly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend-api-design
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100