feat(time_comparison): Support all date formats when computing custom and inherit offsets #30002
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.
SUMMARY
The time comparison feature that's being used in Table and Big Number charts does not support Human Readable dates and it's very limited on what date formats it supports.
Now the API supports sending
inherit
or aYYYY-MM-DD
date as offset value so we can rely on the existing API to parse any date before computing the custom or inherit offset.BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF
Before
Now
TESTING INSTRUCTIONS
Aug 2024
until `tomorrow``ADDITIONAL INFORMATION