You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, Single Stat will only render strings or numbers without any interpretation of what they represent. For example, a timestamp in JavaScript is a number that can be interpreted as milliseconds from a certain time.
Proposal: Allow Single Stat to interpret numbers as timestamps and render a time rather than a number.
Here is an example .csv that will not show a timestamp, but rather just a number.
This requires updating LatestValueTransform to preserve the column type, passing the column type down as props, and then updating formatStatValue to consider the column type.
Currently, Single Stat will only render strings or numbers without any interpretation of what they represent. For example, a timestamp in JavaScript is a number that can be interpreted as milliseconds from a certain time.
Proposal: Allow Single Stat to interpret numbers as timestamps and render a time rather than a number.
Here is an example .csv that will not show a timestamp, but rather just a number.
The output is this but what we really want is a timestamp:
The text was updated successfully, but these errors were encountered: