Hi Ben,
I too predominantly use LocalDateTime in my web applications nowadays,
and any improvements in Tapestry to facilitate this are very welcome.
With regards,
Chris Dodunski.
On 2020-10-20 02:45, David Taylor wrote:
Hi Ben,
A nice addition. We use LocalDateTime and ZonedDateTime in many of our
applications and will make good use of your new type coercers.
Best regards
David
emailsig
On 10/16/2020 4:01 AM, Ben Weidig wrote:
Hi,
it would be great to see the Java Time API better integrated into
Tapestry,
so I've started adding type coercers.
As with my JSON improvements, I've prepared a short proposal to
highlight
the intentions and ramifications better. It's included in the ticket,
which
also already has a patch:
Proposal:
https://gist.github.com/benweidig/e0e7c9a26f3805e610c4511a0a15b9e3
Ticket: https://issues.apache.org/jira/browse/TAP5-2645
Compare:
https://github.com/apache/tapestry-5/compare/master...benweidig:typecoercer-jsr310
I've excluded the more "unusual" types in java.time.chrono, like
JapaneseDate etc.
But if you think they should be included as well, I could create an
additional patch.
Feedback is always welcome.
Cheers
Ben
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org
For additional commands, e-mail: dev-h...@tapestry.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org
For additional commands, e-mail: dev-h...@tapestry.apache.org
