split draft implementations

Open
#83 0 comments 0 reactions 0 assignees View on GitHub

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

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

validator

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

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from openapi-processor/openapi-parser

All issues in openapi-processor/openapi-parser

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.