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
This checking will cause the value to wrongly display to time value, it is quite annoying.
For example 2257757352, we want to display this length of the value in our project, but it displayed '2041-07-18 18:49:12'.
The text was updated successfully, but these errors were encountered:
Now that we have support for setting the type explicitly, I think it's reasonable to not automatically detect Unix epochs. In the meantime, you should be able to fix this by setting the type as Number.
/~https://github.com/marcusolsson/grafana-json-datasource/blob/4352df6d0a48dcbf14597d575a7cbc9f79a2a590/src/datasource.ts#L202-L209
This checking will cause the value to wrongly display to time value, it is quite annoying.
For example 2257757352, we want to display this length of the value in our project, but it displayed '2041-07-18 18:49:12'.
The text was updated successfully, but these errors were encountered: