jakartaee / jakartaee/jsonb-api
Incompatibility with "Schema" based designs
Open
- Dominant language
- Java
- Stars
- 95
- Forks
- 41
- Avg merge
- 1d 6h
- Merged PRs (30d)
- 35
Description
This issue is related to #33
AFAIK all existing schema based designs presume that the type of an element stays the same regardless of its value. The variable type concept for numbers used by jsonb/jsonp breaks that.
Have you performed any interoperability tests with other JSON tools?
Contributor guide
Research direction
Start by reading the relationship to issue #33 and the existing 58-comment discussion about schema-based designs and interoperability. The issue does not name files or tests; work would first require defining which JSON tools and schema cases to test, then agreeing on the compatibility requirements and reporting the results.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100