Conversation
This was referenced Feb 2, 2026
Member
|
Works great! |
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
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.
This PR adds:
An
augment_formatoption to thetimefieldtype.This will allow you to use
{{ time_field }}by itself on the frontend and it will output the appropriate format with needing any modifiers.A
format_timemodifierThis can be chained into a time and will convert it to the given format.
It bypasses any of the timezone logic that the other date modifiers use.
e.g.
{{ "13:45" | format_time('g:ia') }}outputs1:45pmIt will use
g:iaby default so you don't even need to pass the format.e.g.
{{ "13:45" | format_time }}outputs1:45too.Closes #13766