playframework / playframework/play-json
add hook to allow play-json users to provide their own Jackson JsonFactory or ObjectMapper
Nobody has claimed this yet.
- Dominant language
- Scala
- Stars
- 375
- Forks
- 140
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 28
Description
play-json is pretty dependent on Jackson for low level parsing support.
There are some open but not progressed PRs and issues regarding supporting Jackson features. Allowing users to provide their own JsonFactory or ObjectMapper would make it so that play-json users could uptake some of these Jackson features themselves.
Doing this at the JsonFactory level would be better because of the way that Jackson is evolving.
Relates to:
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 play-json's low-level Jackson parsing setup and how JsonFactory and ObjectMapper are currently constructed. Review the related pull request #999 and issue #835, then define the hook at the JsonFactory level so users can supply their own configuration and verify that existing parsing behavior remains supported.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100