2 ms·
> Temporal does not support parsing human-readable strings. Well shit, that's one of the biggest things I want from a time library. There are about 15 differen
by dheera 5y ago
> Temporal does not support parsing human-readable strings.
Well shit, that's one of the biggest things I want from a time library. There are about 15 different forms of human readable string formats that various APIs give you in their JSON responses and if they don't solve that, they haven't solved the biggest pain point.
I guess congratulations for not solving the problem and instead making Javascript even more complicated to use by introducing yet another date library that skirts around perhaps the most important feature.
- dengsauve 5y agoI was equally disappointed to see this feature absent.
- 8bitsrule 5y agoMandatory XKCD. One last time? https://xkcd.com/927/ https://xkcd.com/927/
- lazarljubenovic 5y agoParsing human-readable strings is application-specific. It's good that this is kept in userland. Not matter how they do it, it's not going to work for at least 50% of use-cases. It would result in additional bloat of Temporal that's probably useless to you anyway. How do you parse (and do you parse) “01. 02. 2003.”, “jan 2 2003”, “2nd jan '03”, “today”, and “tomorrow night”? The API should parse only the ISO standard(s).