- Issue created by @Chi
- 🇮🇳India pradhumanjainOSL
pradhumanjain2311 → made their first commit to this issue’s fork.
- Merge request !6085Issue #3411922: Increase max allowed granularity in Time ago formatter → (Closed) created by Unnamed author
- Status changed to Needs review
almost 2 years ago 12:27pm 9 January 2024 - Status changed to Needs work
almost 2 years ago 2:31pm 9 January 2024 - 🇺🇸United States smustgrave
Think we should be able to extend some test coverage somewhere for this.
- 🇮🇳India TanujJain-TJ
Tanuj. → made their first commit to this issue’s fork.
- Status changed to Needs review
almost 2 years ago 7:19am 25 January 2024 - Assigned to dishakatariya
- Issue was unassigned.
- Assigned to divya.sejekan
- Issue was unassigned.
- Status changed to RTBC
almost 2 years ago 1:04pm 25 January 2024 - 🇮🇳India divya.sejekan
Tested using - MR!6085
The issue is fixed.Testing steps :
Steps to reproduce
Add timestamp field to some content type.
Set the granularity formatter setting to max allowed value which is 6.
Create a node and set the timestamp value to some date far in the past.
Notice that the rendered interval does not include seconds.Can Be Moved to RTBC++
- 🇺🇸United States smustgrave
@Tanuj same deal as the other one, this was tagged for a novice user to get started. Based on your post history you should be able to work on non novice issues
- 🇮🇳India TanujJain-TJ
hey sure @smustgrave will keep that in mind. thanks
-
longwave →
committed dfe15ca8 on 11.x
Issue #3411922 by pradhumanjain2311, Tanuj., divya.sejekan, Chi,...
-
longwave →
committed dfe15ca8 on 11.x
- Status changed to Fixed
over 1 year ago 5:38pm 3 February 2024 Automatically closed - issue fixed for 2 weeks with no activity.