Jackson 3 support
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Quiet
- Domain
- api, backend-api-design
Research direction
Start by reading the SchemaParserOptions APIs and the PerFieldObjectMapperProvider and PerFieldConfiguringObjectMapperProvider interfaces named in the issue. Compare their Jackson 2 types with Jackson 3's tools.jackson.databind.ObjectMapper, then assess the two proposed compatibility approaches. Done means users can upgrade to Spring Boot 4 without retaining Jackson 2 dependencies, with the chosen API approach and its compatibility tradeoffs defined.
Written by the indexing model from the issue text.
Description
I want to suggest an idea and checked that ...
- ... to my best knowledge, my idea wouldn't break something for other users
- ... the documentation does not mention anything about my idea
- ... there are no open or closed issues that are related to my idea
Description
Jackson 3.x has been released with a package rename from com.fasterxml.jackson to tools.jackson. Spring Boot 4.0 ships with Jackson 3 by default.
Projects upgrading to Spring Boot 4 that use graphql-java-tools are currently blocked from fully migrating off Jackson 2 because SchemaParserOptions requires a com.fasterxml.jackson.databind.ObjectMapper.
Affected API
- SchemaParserOptions.objectMapperProvider
- SchemaParserOptions.objectMapperConfigurer
- PerFieldObjectMapperProvider / PerFieldConfiguringObjectMapperProvider
###Request
Add support for Jackson 3's tools.jackson.databind.ObjectMapper, either by:
- Migrating to Jackson 3 directly (breaking change)
- Supporting both via separate APIs or an abstraction layer
Use Cases
Allows users to upgrade to Spring Boot 4 without retaining legacy Jackson 2 dependencies.
- Dominant language
- Kotlin
- Stars
- 824
- Forks
- 175
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 52
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from graphql-java-kickstart/graphql-java-tools
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
graphql-java-kickstart/graphql-java-tools#893 ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 72/100
graphql-java-kickstart/graphql-java-tools#889 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 55/100
graphql-java-kickstart/graphql-java-tools#886 ·
Maintainers usually reply within 1 day
-
Reject directives applied at the wrong location, without a required argument or twice in 15.0.0Openenhancement
Difficulty 3/5 1-2 days Newbie friendliness 72/100
graphql-java-kickstart/graphql-java-tools#884 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
graphql-java-kickstart/graphql-java-tools#881 ·
Maintainers usually reply within 1 day
All issues in graphql-java-kickstart/graphql-java-tools
Similar issues
-
area/kotlin
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
dafonton77-tech/Cadreenf#11 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
Hy4ri/hermes-mobile#1647 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
rawnaldclark/Stash#649 ·
Maintainers usually reply within 1 day