-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
Create proper MonthDeserializer
and MonthSerializer
(don't rely on EnumDeserializer
/EnumSerializer
)
#5078
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
MonthDeserializer
(don't rely on EnumDeserializer
)MonthDeserializer
and MonthSerializer
(don't rely on EnumDeserializer
/EnumSerializer
)
@JooHyukKim this might be something for you, wrt date/time ser/deser. Basically: although |
Thanksss, I will look into this! |
@cowtowncoder Since there is behavior change, can we add |
Sure, added. Feel free to add labels as necessary (you have access, right? If not I can see how to give access) EDIT: requires "Triage" access. |
Yeah it would help 👌🏼 for label access |
@JooHyukKim created new team ("core contributors") with Triage access so you and @pjfanning should now be able to add/remove labels on jackson-databind issues. Also LMK where else needed (will add to |
Current deserializer implementation for type
java.time.Month
is a mess, inherited fromjackson-datatype-jsr310
: it defaults to using plainEnumDeserializer
but wrapping it in case of 1-based processing being enabled.Instead, we should just write regular deserializer.
The text was updated successfully, but these errors were encountered: