Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

v5.9.0 Issues with Datetime in several stories #479

Closed
acblackford opened this issue Nov 5, 2024 · 2 comments · Fixed by #481
Closed

v5.9.0 Issues with Datetime in several stories #479

acblackford opened this issue Nov 5, 2024 · 2 comments · Fixed by #481
Labels
bug Something isn't working

Comments

@acblackford
Copy link
Contributor

I have noticed that datetime formatting in several published stories that were previously working are no longer working following the release of v5.9.0. Attached is an example, but both time series and spatial data have these issues in a few stories such as Darnah, Burn Scar, and Lahaina. I am not sure if this is a bug or was intentional and I need to go in to these stories to fix the formatting of these dataset visualizations?

image
@acblackford acblackford added the bug Something isn't working label Nov 5, 2024
@dzole0311
Copy link
Collaborator

I think the "DD LLL yyyy" date format error is actually expected. We didn't catch this earlier since we were running an old version of the veda-ui in the veda-config repo. It's probably better to just update the date format in the stories directly.

I went ahead and checked other instances and they all seem to be using the correct date formatting.

This was referenced Nov 6, 2024
@j08lue
Copy link
Contributor

j08lue commented Nov 6, 2024

The linked PR seems to fix the date formatting issue.

I checked only the Darnah flood story. https://deploy-preview-481--visex.netlify.app/stories/darnah-flood

But I noticed two other issues with the map embedded in that story:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants