Philippe SEGATORI

@BenMorel If you could take a quick look about this one, it's pretty straight forward. It's slightly related to https://github.com/brick/date-time/issues/55

@BenMorel FYI I'm waiting for this to be merged and make sure it works as expected before opening the related PR to other brick projects

@BenMorel digging a bit more about the inclusion of psalm as a shared tool for the org, I found that a `brick/static-analysis` repo might be needed. Actually, doctrine doesn't share...

@BenMorel friendly ping 😉

Hey @BenMorel, hope your vacations went well :slightly_smiling_face:. If you can find some time to help moving this topic forward I'll be available. Thanks in advance.

Hello, We have more or less the same use case. Part of our application *must* preserve UTC as a timezone to comply with business rules. We introduced an `UTCDateTime` decorating...

It's understandable but like @BenMorel pointed out here: https://github.com/brick/date-time/issues/8#issuecomment-526817214 this is not ideal. Decorating and providing a `toZonedDateTime()` would also allow what you describe. Giving you the best of both...

@mabar It could but when you manipulate `ISO 8601` formatted date from your database and web context, using `Instant` would force you into superfluous conversion. ```php // From POST request...

FYI, we've talked about it with @BenMorel some weeks ago, he got the point but he's still undecided and needs to process the implications. In the meantime, take a look...

`ZonedDateTime` can handles multiple timezone while `UTCDateTime` only have one and should not care about timezone at all. However if you rely on the `ZonedDateTime` api to represent an `UTCDateTime`...