Hacktoberfest 2026:維護者為十月標記出來的 issue,仍然開放、適合新手。 瀏覽 Hacktoberfest issue

Jackson 3 support

未關閉
#810 2 則留言 2 個 reaction 已指派 0 人 在 GitHub 檢視

維護者通常 1 天內回覆

還沒有人認領這個 Issue。

評估

難度
5/5
預估耗時
一週以上
新手友好度
35/100
Issue 類型
功能
描述清晰度
基本清楚
活躍度
冷清
技術堆疊
java, kotlin, spring-boot

研究方向

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.

由索引模型根據 Issue 內容生成。

描述

enhancement

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.

主要語言
Kotlin
星號
824
分支
175
平均合併
2 天 5 小時
30 天內合併 PR
52

環境準備

這個專案沒有提供開發容器、Dockerfile 或貢獻指南,環境需要你自己搭建:先看它的 README,通用步驟見我們的新手貢獻指南。

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

graphql-java-kickstart/graphql-java-tools 的其他 Issue

查看 graphql-java-kickstart/graphql-java-tools 的全部 Issue

相似的 Issue

更多 Kotlin Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。