[GH-ISSUE #1220] JsonSerializable implementation for DateTime #509

Closed
opened 2026-03-04 02:15:35 +03:00 by kerem · 4 comments
Owner

Originally created by @Olegf13 on GitHub (Nov 7, 2018).
Original GitHub issue: https://github.com/Seldaek/monolog/issues/1220

Hello. Found next change in repo history committed in master but not yet included into any release - github.com/Seldaek/monolog@6bb347c040/src/Monolog/DateTimeImmutable.php

Is there a way to include this change in one of nearest releases for the 1.x branch?

Originally created by @Olegf13 on GitHub (Nov 7, 2018). Original GitHub issue: https://github.com/Seldaek/monolog/issues/1220 Hello. Found next change in repo history committed in master but not yet included into any release - https://github.com/Seldaek/monolog/blob/6bb347c040bb29f42c2c249714aac8c0e36c2454/src/Monolog/DateTimeImmutable.php Is there a way to include this change in one of nearest releases for the 1.x branch?
kerem closed this issue 2026-03-04 02:15:36 +03:00
Author
Owner

@Olegf13 commented on GitHub (Nov 7, 2018):

Sorry, forgot to describe the problem. At the moment in case of using JsonFormatter there is a problem with datetime to json serializing. Result log looks like the following:

"datetime":{"date":"2018-11-06 17:41:54.310231","timezone_type":3,"timezone":"Europe/Moscow"}
<!-- gh-comment-id:436626150 --> @Olegf13 commented on GitHub (Nov 7, 2018): Sorry, forgot to describe the problem. At the moment in case of using `JsonFormatter` there is a problem with datetime to json serializing. Result log looks like the following: ``` "datetime":{"date":"2018-11-06 17:41:54.310231","timezone_type":3,"timezone":"Europe/Moscow"} ```
Author
Owner

@moderndeveloperllc commented on GitHub (Nov 7, 2018):

@Olegf13 That whole class is part of the "2.x" release code in master. It won't be released until @Seldaek is happy with the state of master and creates that release. I've been using dev-master in my composer.json files for a couple of years now. He keeps a tight quality control over what gets in, so it's reasonable safe.

<!-- gh-comment-id:436657503 --> @moderndeveloperllc commented on GitHub (Nov 7, 2018): @Olegf13 That whole class is part of the "2.x" release code in master. It won't be released until @Seldaek is happy with the state of `master` and creates that release. I've been using `dev-master` in my `composer.json` files for a couple of years now. He keeps a tight quality control over what gets in, so it's reasonable safe.
Author
Owner

@Seldaek commented on GitHub (Nov 19, 2018):

See https://github.com/Seldaek/monolog/milestone/1 - we're getting there.

<!-- gh-comment-id:440078203 --> @Seldaek commented on GitHub (Nov 19, 2018): See https://github.com/Seldaek/monolog/milestone/1 - we're getting there.
Author
Owner

@Olegf13 commented on GitHub (Nov 20, 2018):

@moderndeveloperllc, @Seldaek thank you for your answers!

<!-- gh-comment-id:440219290 --> @Olegf13 commented on GitHub (Nov 20, 2018): @moderndeveloperllc, @Seldaek thank you for your answers!
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/monolog#509
No description provided.