dateparse icon indicating copy to clipboard operation
dateparse copied to clipboard

GoLang Parse many date strings without knowing format in advance.

Results 65 dateparse issues
Sort by recently updated
recently updated
newest added

I've fixed the errors with date formats with the leading date: 02.01.2006, 02/01/2006. Without fix the ParseAny function was returning the error "month out of range". Tests were added.

] $ dateparse --timezone="America/Denver" "Dec 4 10:19" fatal: parsing time "Dec 4 10:19" as "Jan 2 10:19": cannot parse ":19" as "0:" Thanks, but I'll look for another utility to...

timestamps like "1573583039.370" will be parsed like "1573583039370" without the dot. related to: #121

for this float timestamp in sec 1573583039.370 it should parse as 2019-11-12T18:23:59.369Z in format "2006-01-02T15:04:05.000Z". but it's not happening and getting "1573583039.370": hour out of range error.

Some European dates are formatted as dd-mm-yyyy where day month and year are all digits. Fixes #139 Signed-off-by: Daniel Ferstay

`31 ott 2021 23:37:13 UTC` ott is the abbreviation of Italian month.

, although they obviously don't. I have prepared a test case replicating the problem and mocked the string we found it with. But I hope the committed one replicates the...

We have support for dates of the form `dd-mmm-yy` where `mmm` is an alphanumeric literal; for example: ``` "15-Jan-2017" ``` However, there is a European date format that is similar...

We have support for a unixy combined timstamp format of the form `yyyyMMddhhmmss` However, some systems log with subseconds appended, for example: ``` 20140722105203.364 ``` The above should parse as:...