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
futureStringTwo outputs 8 minutes ago.
I would expect both string to be in 8 minutes.
Also, all the parameters passed in colloquialSinceNow are ignored, it will always return the same string no matter what other parameters I pass in the function.
I'm using version 4.0.8.
Thanks
The text was updated successfully, but these errors were encountered:
Hi,
Okay that's clearly a bug; when gap between two dates is expressed in minutes the value in your example is -8 and -8 < 5 minutes, so it's wrong perceived in "just now" case.
I've solved it in this commit 88067f1. You will found it in 4.0.9 upcoming release.
Thank you
malcommac
changed the title
Colloquial & ColloquialSinceNow issues
Colloquial report wrong "just now" when gap between dates are expressed in minutes and the left comparing date is future
Dec 19, 2016
Hey there, I believe there are still a couple of issues in Colloquial and ColloquialSinceNow.
Given the following code:
futureStringOne
outputsjust now
futureStringTwo
outputs8 minutes ago
.I would expect both string to be
in 8 minutes
.Also, all the parameters passed in colloquialSinceNow are ignored, it will always return the same string no matter what other parameters I pass in the function.
I'm using version 4.0.8.
Thanks
The text was updated successfully, but these errors were encountered: