Consider using `ChronoZonedDateTime`
See original GitHub issueCurrently, a concrete implementation (ZonedDateTime
) is used, making it impossible to do lazy parsing.
If ChronoZonedDateTime
(ZonedDateTime
implements it) is used in the public API, it will provide the same set of useful APIs, but allow better flexibility.
Issue Analytics
- State:
- Created 3 years ago
- Comments:11 (11 by maintainers)
Top Results From Across the Web
ChronoZonedDateTime from() method in Java with Examples
The from() method of ChronoZonedDateTime interface in Java method obtains an instance of ChronoZonedDateTime from a temporal object. Syntax:.
Read more >ChronoZonedDateTime (Java Platform SE 8 )
A date-time with a time-zone in an arbitrary chronology, intended for advanced globalization use cases. Most applications should declare method signatures, ...
Read more >How convert LocalDate to ChronoZonedDateTime?
This gives the conversion that was asked for and works as a solution. I think it's easier to use the opposite conversion as...
Read more >java.time.chrono.ChronoLocalDateTime.compareTo ... - Tabnine
The comparison is based first on the underlying time-line date-time, then on the chronology. It is "consistent with equals", as defined by Comparable....
Read more >ZonedDateTime (Java SE 11 & JDK 11 )
Obtains an instance of ZonedDateTime from an Instant . This creates a zoned date-time with the same instant as that specified. Calling ChronoZonedDateTime....
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Yes, please reopen it. Closing legitimate issues before giving it due process and reasonable debate will eventually discourage community participation all together, which would be detrimental and quite frankly unfair to the entire Cloud Events and Cloud Native Computing Foundation effort, don’t you think?
Because now we use
OffsetDateTime
, this issue is not valid anymore (OffsetDateTime
doesn’t extendChronoZonedDateTime
). Check out the release docs https://github.com/cloudevents/sdk-java/releases/tag/2.0.0-milestone2 and the pr https://github.com/cloudevents/sdk-java/pull/216 for more info