JSON schemas
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
No files, response types, or tests are named in the issue. Start by locating the response definitions and the existing JSON handling, then identify every response that needs a schema and validation; done means each response has a schema and invalid JSON is rejected by validation.
Written by the indexing model from the issue text.
Description
Create JSON schemas for each response and then add JSON validation.
- Dominant language
- Java
- Stars
- 23
- Forks
- 15
- PR merge metrics
- No merged PRs in 30d
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.
More from Laffini/Java-Matching-Engine-Core
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Difficulty 3/5 1-2 days Newbie friendliness 20/100
-
good first issue
Difficulty 3/5 1-2 days Newbie friendliness 35/100
-
documentation
Difficulty 4/5 3-5 days Newbie friendliness 35/100
All issues in Laffini/Java-Matching-Engine-Core
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
infinispan/infinispan#18150 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
opensearch-project/k-NN#3597 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100