Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Make LocalDateDeserializer consider strict/lenient on accepting (or not) of "time" part #212

Closed
cowtowncoder opened this issue Mar 26, 2021 · 0 comments
Closed

Make LocalDateDeserializer consider strict/lenient on accepting (or not) of "time" part #212

cowtowncoder opened this issue Mar 26, 2021 · 0 comments
Milestone
2.13.0

Comments

@cowtowncoder
Copy link
Member

Currently LocalDateDeserializer automatically accepts non-standard format where time part also exists.
While this is useful for some use cases, compatibility, it seems reasonable that if user forces "strict" handling (via @JsonFormat, or global default), that part would not be accepted. This is in line with similar handling on LocalDateTimeDeserializer, with respect to handling of non-compliant timezone (Z) suffix.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
2.13.0
Development

No branches or pull requests
1 participant
@cowtowncoder