-
Notifications
You must be signed in to change notification settings - Fork 38.3k
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
Add support for instant in @DateTimeFormat #19846
Comments
Krzysztof Krason commented Any updates here? Is this behavior intentional? |
Krzysztof Krason commented Juergen Hoeller Any updates? |
I assume the main difficulty in implementing this feature is passing zone id(since you can't format an Instant without zone id: https://stackoverflow.com/questions/25229124/format-instant-to-string) to this formatter: |
How come this actually doesn't work for me? The exact same above sample throws an parser exception What I noted is that Secondly, the @snicoll any ideas? |
@eldarj, this issue was closed over a year ago. If you feel that you have encountered a bug, please create a new issue and provide a minimal example that reproduces the behavior. As for why |
@sbrannen Thanks a lot for the quick tip, and sure, I'll double check further and open a new issue if needed. Ty! |
Krzysztof Krason opened SPR-15280 and commented
@DateTimeFormat
annotation is supported by all Java 8 time classes except Instant, which always assumes the date is in the format "2017-02-21T13:00:00Z".Right now when making a request with start set to 2017-02-21T13:00, following code works (uses LocalDateTime):
But following doesn't (fails with parsing exception):
Affects: 4.3.6
1 votes, 2 watchers
The text was updated successfully, but these errors were encountered: