bowtie-json-schema / bowtie-json-schema/bowtie
Add support for running `v1` from the test suite
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 94
- Forks
- 77
- Avg merge
- 10h 29m
- Merged PRs (30d)
- 40
Description
data/dialects.json lists six dialects, ending at 2020-12. The JSON Schema test suite has carried a tests/v1 directory for a while now, and implementations have started supporting it, but there is no way to declare that in Bowtie or to run the report against it.
Adding an entry would need at least:
data/dialects.json: a v1 entry with https://json-schema.org/v1 as its URI, plus whatever firstPublicationDate and prettyName shape the other entries use.
the suite loader pointing at tests/v1, which already exists upstream.
implementations opting in by adding the URI to the dialects array they return from start.
Contributor guide
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
Start with data/dialects.json and compare the existing dialect entries, then locate the suite loader that selects tests directories. Check the upstream tests/v1 layout and how implementations return their dialects array. Done means v1 is declared, tests/v1 is runnable, and implementations can opt in using its URI.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- json, python
- Domain
- testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100