Transformations: Support time format when converting time to strings #63826
Conversation
This file contains 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
ryantxu
added
add to changelog
area/transformations
no-backport
ryantxu
commented
Mar 1, 2023
ryantxu
requested review from
tskarhed,
yaelleC and
academo
and removed request for
a team
ryantxu
changed the title
leeoniya
approved these changes
Mar 2, 2023
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.
Currently when using transformers to convert a time to string, we render the unix milliseconds as a string -- this is less helpful than people would like :)
This PR uses the 'dateFormat' option to format times when converting from a time field.
See also #63828 and #63827 for an improved UX