jakartaee / jakartaee/jsonb-api
Support for complex (non-String) JSON keys
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 95
- Forks
- 41
- Avg merge
- 1d 6h
- Merged PRs (30d)
- 35
Description
At the moment, MapDeserializer throws an error if the key for the Map is not a String. Can we add a feature to allow the JSONConfig to have a custom deserializer for the Key, like in Jackson? Or Can we extend the Deserializer framework to allow registering custom Deserializers for a Map? At the moment, Deserializers can be registered for other datatypes through Adapters but not for a Map.
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 by tracing MapDeserializer and reviewing how JSONConfig and Adapters currently register deserializers. Clarify with maintainers whether custom key deserializers, custom Map deserializers, or both are required; the work is complete when the agreed approach supports non-String Map keys and is covered by appropriate tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100