Use dateFormat function to render localized dates #355
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.
This PR fixes the date not being rendered honoring the content localization.
🪲 Found bug
The dates were rendered using the .Format function which does not follow the content localization.
Example: the date
2023-06-07
was rendered as "7 June 2023" inside an Italian content.✅ Applied fix
The fix replaces the
.Format
function with the dateFormat one, which respects the page localization. Going on with the example above, the Italian content now renders the same date as "7 giugno 2023" which is the expected output.