1-01-2016 → D-MM-YYYY

[hillmanov]

moment.parseFormat('1-01-2016') parsed to D-M-YYYY, I expected: D-MM-YYYY

[gr2m]

Thanks @hillmanov! Out of curiosity, is this date format (DMY with - as separator) common at your company or the region where you are from? I’ve never seen it before. Usually people use . as separator for DMY and use - for YMD

[hillmanov]

@gr2m No, not very common, but we have seen it.

The issue that we have where I work is we pull a lot of data from APIs and deal with user input and need to detect date formats off that. So, whatever the API returns, we have that to work with!

[gr2m]

Okay I don’t mind adding it to the parser. Can you send a pull request for it? Start by adding a test here: https://github.com/gr2m/moment-parseformat/blob/master/test/moment-parseformat-test.js then figure out the implementation :)

[thenexus00]

I know this is old but I have actually identified the issue

IF you are doing:
1-January-2021 or 02-January-2021

IF You output stagings of the format value:

02-MMMM-2021 -> This is before it gets to the time format aspect
02-MMMMZ -> This is what happens after the time format

If you comment out the time format section in the code it all works.

What I think you need to have is the Year Format before the time and this and a few use cases where it produces an invalid date it can reformat.

[taras-budzyn]

Have a similar issue when working with Date 3.11.2022.
I see that issue is quite old one, is it resolved already?

[konradzawadka]

Yes, PR is opened Am Mo., 14. Nov. 2022 um 16:18 Uhr schrieb taras-budzyn < ***@***.***>:

…

Have a similar issue when working with Date 3.11.2022. I see that issue is quite old one, is it resolved already? — Reply to this email directly, view it on GitHub <#52 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABIAXFKUXHZ3KXY72KPF27LWIJJ53ANCNFSM4CGWGB4A> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[konradzawadka]

But, it looks on other issue. Your problem is fixed in major version Am Mo., 14. Nov. 2022 um 16:18 Uhr schrieb taras-budzyn < ***@***.***>:

…

Have a similar issue when working with Date 3.11.2022. I see that issue is quite old one, is it resolved already? — Reply to this email directly, view it on GitHub <#52 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABIAXFKUXHZ3KXY72KPF27LWIJJ53ANCNFSM4CGWGB4A> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>