This repository has been archived by the owner on Sep 9, 2024. It is now read-only.
feat: fallback to date-fns.parseISO when date cannot be parsed #1080
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.
I am migrating a website from Decap/NetlifyCMS and I have an issue with existing dates not being parsed.
The dates are stored as
2024-02-25T18:30:00.000Z
(ISO format) and date-fns tries to parse it with the format"yyyy-MM-dd'T'HH:mm:ssXXX"
(which does not raise an exception, but returns an Invalid Date): https://date-fns.org/v3.3.1/docs/parseI don't mind storing them with the static-cms default, however it would be nice if static-cms could try harder to parse the date (instead of showing an empty date, losing the data).