jakartaee / jakartaee/jsonb-api

Character Encoding

Open
#228 1 comment 0 reactions 0 assignees View on GitHub
TCK
Dominant language
Java
Stars
95
Forks
41
Avg merge
1d 6h
Merged PRs (30d)
35

Description

The JSON-B specification mentions "Instances of [...] java.lang.Character are serialized to JSON String values as defined within RFC 7159 Section 7 (Strings)". The RFC (https://tools.ietf.org/html/rfc7159#section-7) mentions that "All Unicode characters may be placed within the quotation marks, except for the characters that must be escaped: quotation mark, reverse solidus, and the control characters (U+0000 through U+001F)."

Now the problem is that there is a TCK test `BasicJavaTypesMappingTest#testCharacterMapping` that tests that Character.MAX_VALUE (= '\uFFFF') is escaped. U+FFFF falls outside of U+0000 through U+001F, so I assume that this character does not need to be escaped. Does that mean that the test is making a stronger assumption than necessary?

Contributor guide

Open the contributing guide

Research direction

Read RFC 7159 Section 7 and the JSON-B wording, then inspect BasicJavaTypesMappingTest#testCharacterMapping. Determine whether requiring escaping U+FFFF is mandated; done means the issue has a documented resolution and the TCK expectation is aligned with the agreed interpretation.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
api, testing-qa
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.