split draft implementations
Maintainers usually reply within 2 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Refactor
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- java
- Domain
- backend-api-design
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.
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
- ...
- Dominant language
- Java
- Stars
- 27
- Forks
- 2
- Avg merge
- 3d 19h
- Merged PRs (30d)
- 13
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from openapi-processor/openapi-parser
-
Jackson 3 supportOpenenhancement
Difficulty 5/5 Over a week Newbie friendliness 20/100
openapi-processor/openapi-parser#159 ·
Maintainers usually reply within 2 days
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 25/100
openapi-processor/openapi-parser#120 ·
Maintainers usually reply within 2 days
-
Difficulty 4/5 3-5 days Newbie friendliness 30/100
openapi-processor/openapi-parser#95 · 6 comments ·
Maintainers usually reply within 2 days
-
parser
Difficulty 5/5 Over a week Newbie friendliness 25/100
openapi-processor/openapi-parser#82 ·
Maintainers usually reply within 2 days
-
OpenAPI 4.0 supportOpenparser
Difficulty 5/5 Over a week Newbie friendliness 15/100
openapi-processor/openapi-parser#81 ·
Maintainers usually reply within 2 days
All issues in openapi-processor/openapi-parser
Similar issues
-
Heavy legs 1.12–1.17: compiler corpus goldens not regenerated for #4770Possibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
intellij-elixir/intellij-elixir#4782 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
模组数量显示不一致Openbug/错误
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
FCL-Team/FoldCraftLauncher#2034 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
openapi-processor/openapi-processor-spring#524 ·
Maintainers usually reply within 2 days
-
ManageSieve HAVESPACE answers OK for an empty script name, which PUTSCRIPT refusesPossibly taken @chibenwa claimed this today. Openai-driven-qa bug claude Cosmetic
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
linagora/tmail-backend#3062 · 2 comments ·
Maintainers usually reply within 1 day