Hacker News Reader

Comment by omnicognate | Hacker News Reader

Should have included the units in the name or required a choice of unit to be selected as part of the value. Sorry, just a bugbear of mine.

View on HN

The new setting is consistent with the old ones, which is more important IMHO:

https://pnpm.io/settings#modulescachemaxage

the name could have included it though right?

If the others don't include it, it could be another inconsistance though

Or just use ISO8601 standard notation (e.g. "P1D" for one day)

or PT1400M or P0.5DT700M?

oh, you can use commas too.

and if you're still not thinking this is fun, here's a quote from Wikipedia "But keep in mind that "PT36H" is not the same as "P1DT12H" when switching from or to Daylight saving time."

just add a unit to your period parameters. sigh.

Maybe surprising for days (could also happen with minutes because of leap seconds technically :-) but for months and years this is more apparent due to month ends and leap years.

TIL ISO8601 also standardizes duration

ISO8601 durations should be used, like PT3M.

Oh wow, never looked at ISO8601 durations before and I had no idea they were this ugly. Please, no, don't make me deal with ISO8601. I'd rather write a number of seconds or a format like 'X weeks' or 'Y hours Z minutes'x ISO8601 looks exclusively like a data interchange format

https://docs.digi.com/resources/documentation/digidocs/90001...

It's pretty simple actually.

> 'X weeks' or 'Y hours Z minutes'

PxW, PTyHzM. So simple that I learned it in a few seconds.

I learned it too. It's just ugly. Before I looked at the relevant section of the ISO 8601 duration format yesterday, I didn't know it. After I looked at it, I now know it, and I strongly dislike it.

When in doubt, use only seconds. PT86400S

Should be easy, just add the ISO8601-duration package to your project ..

Reply on news.ycombinator.com