fix: support custom TimeFormat for console formatter - #136
Merged
Conversation
nrwiersma
requested changes
Jul 19, 2026
Deprecate TimeFormatUnix and replace it with TimeFormatDefault.
nrwiersma
requested changes
Jul 19, 2026
nrwiersma
reviewed
Jul 22, 2026
nrwiersma
approved these changes
Jul 22, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Goal of this PR
Support using a different TimeFormat than
time.Kitchenfor the console formatter.TimeFormatUnixand usesTimeFormatDefaultinstead, keeping the use oftime.Unix()as a default.TimeFormatConsoleset totime.Kitchenas before, but can now be changed.How did I test it?