json-schema-org / json-schema-org/referencing
Non-object root values
Open
Nobody has claimed this yet.
jri
- Dominant language
- Makefile
- Stars
- 9
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
(Breaking out https://github.com/json-schema-org/referencing/pull/2#discussion_r1004993311 into an issue.)
While it probably makes sense in most use cases, it's possible that the root value of a document could be an array or other valid JSON value.
The spec should have language that accounts for this.
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
No file or test is named. Start with the referenced pull request discussion and inspect the repository's current specification material; determine how root arrays and other valid JSON values should be covered. Done means the specification clearly accounts for non-object root values.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- json
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100