mirror of
https://github.com/Seldaek/monolog.git
synced 2026-04-27 08:35:53 +03:00
[GH-ISSUE #1220] JsonSerializable implementation for DateTime #509
Labels
No labels
Bug
Documentation
Feature
Needs Work
Support
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/monolog#509
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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.phpIs there a way to include this change in one of nearest releases for the 1.x branch?
@Olegf13 commented on GitHub (Nov 7, 2018):
Sorry, forgot to describe the problem. At the moment in case of using
JsonFormatterthere is a problem with datetime to json serializing. Result log looks like the following:@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
masterand creates that release. I've been usingdev-masterin mycomposer.jsonfiles for a couple of years now. He keeps a tight quality control over what gets in, so it's reasonable safe.@Seldaek commented on GitHub (Nov 19, 2018):
See https://github.com/Seldaek/monolog/milestone/1 - we're getting there.
@Olegf13 commented on GitHub (Nov 20, 2018):
@moderndeveloperllc, @Seldaek thank you for your answers!