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
If we flatten the JSON it will look like this in the table
I patched this issue back in December, but it seems like data has been updated since then and update did not include a fix for this. Worth noting that current tabular version of the data seems to be not affected by the issue.
Or could it be, that current version of the data is not correct? I'm checking version labeled "v3" against version labelled "current" and it seems like "v3" doesn't have those issues with date format (#18 ) and this artifact.
The text was updated successfully, but these errors were encountered:
There is an artifact from our JSON template that eneded up being in the current version of the publication:
In JSON version it looks like this
If we flatten the JSON it will look like this in the table
I patched this issue back in December, but it seems like data has been updated since then and update did not include a fix for this. Worth noting that current tabular version of the data seems to be not affected by the issue.
Or could it be, that current version of the data is not correct? I'm checking version labeled "v3" against version labelled "current" and it seems like "v3" doesn't have those issues with date format (#18 ) and this artifact.
The text was updated successfully, but these errors were encountered: