Skip to content
This repository has been archived by the owner on Jun 27, 2023. It is now read-only.

Send all the precisions we have in the dates #20

Merged
merged 3 commits into from
Sep 1, 2022
Merged

Conversation

Jorropo
Copy link
Contributor

@Jorropo Jorropo commented Aug 18, 2022

Workaround attempt for ipfs/kubo#8762 while nextToken is being speced and implemented.

This need testing I'm not sure all pinning services support this date format.

Copy link
Member

@lidel lidel left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I smoke tested this in ipfs/kubo#9206 (comment) and looks fine.

On the formal side of things, our OpenAPI spec defines these fields as date-time, which is defined by RFC 3339, section 5.6 and optional time-secfrac is part of that spec. I've updated examples in ipfs/pinning-services-api-spec#104 but it is only documentation change.

I think this is 👍 – feel free to merge and tag a patch release, and then bubble it up to ipfs/kubo#8762

@Jorropo
Copy link
Contributor Author

Jorropo commented Aug 18, 2022

I dont want to merge before 0.15 is out.
I can merge here but want to avoid bubling.

@Jorropo Jorropo merged commit 7229a89 into ipfs:master Sep 1, 2022
@Jorropo Jorropo deleted the RFC3339 branch September 1, 2022 11:46
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants