| ▲ | omnicognate 6 days ago |
| 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. |
|
| ▲ | homebrewer 6 days ago | parent | next [-] |
| The new setting is consistent with the old ones, which is more important IMHO: https://pnpm.io/settings#modulescachemaxage |
| |
| ▲ | rtpg 6 days ago | parent [-] | | the name could have included it though right? | | |
| ▲ | TheRoque 5 days ago | parent [-] | | If the others don't include it, it could be another inconsistance though |
|
|
|
| ▲ | zokier 6 days ago | parent | prev | next [-] |
| Or just use ISO8601 standard notation (e.g. "P1D" for one day) |
| |
| ▲ | 1oooqooq 6 days ago | parent | next [-] | | 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. | | |
| ▲ | brewmarche 5 days ago | parent [-] | | 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. |
| |
| ▲ | johanyc 5 days ago | parent | prev [-] | | TIL ISO8601 also standardizes duration |
|
|
| ▲ | fzeindl 6 days ago | parent | prev [-] |
| ISO8601 durations should be used, like PT3M. |
| |
| ▲ | mort96 6 days ago | parent | next [-] | | 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 | | | |
| ▲ | aa-jv 6 days ago | parent | prev [-] | | Should be easy, just add the ISO8601-duration package to your project .. /s |
|