-
-
Notifications
You must be signed in to change notification settings - Fork 272
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
add ISO8601 duration formatting #4343
Conversation
🦋 Changeset detectedLatest commit: 1e4c3c0 The changes in this PR will be included in the next version bump. This PR includes changesets to release 35 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
88a9ef1
to
3489bac
Compare
bbe556f
to
df7f007
Compare
I can't think of an argument against imho |
df7f007
to
d425963
Compare
Alright, let's do it then! |
b9d4a6f
to
1e4c3c0
Compare
147d0a7
to
0e9616f
Compare
2940151
to
71c9d49
Compare
/** | ||
* Formats a Duration into an ISO8601 duration string. | ||
* | ||
* The ISO8601 duration format is generally specified as P[n]Y[n]M[n]DT[n]H[n]M[n]S. However, since |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@gcanti whoops. I forgot to remove this comment. I decided to go with 30 days per month qnd 365 days per year instead.
Should we add this? If so, I'd add a parser implementation too. The spec isn't clear on how to deal with months and years but I left them out anyways for now which is in line with our existing Duration implementation which also doesn't handle those.
Closes #4319