Closed vrunjeti closed 6 years ago
the sorting values are resulting in NaN
for some values
played around with it, it looks like the year 512
was the one causing issues with utc. when that map year isn't in the story, the sorting works. closing this issue since dealing with years like 512 is an edge case we shouldn't really have to worry about considering nnb's specific use case
the format the api sends looks like: Fri, 01 Jan 512 00:00:00 GMT
. played around with it some more, and using 01 Jan 512 00:00:00 GMT
is valid. maybe if we chop off the day part of the string, it'll work from year 0 onwards
we need to change the format of the date the api sends because
moment
isn't able to sort the dates properly: