Skip to content
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

specs-go: Image.Created uses a string type #534

Merged
merged 1 commit into from
Jan 27, 2017
Merged

specs-go: Image.Created uses a string type #534

merged 1 commit into from
Jan 27, 2017

Conversation

jlbutler
Copy link
Member

Modify History.Created and Image.Created to be of type time.Time so that creation times may be validated, compared, etc.

@stevvooe
Copy link
Contributor

stevvooe commented Jan 26, 2017

LGTM

Surprised that we don't have real tests for this but let's not hold up this PR.

@opencontainers/image-spec-maintainers PTAL

Approved with PullApprove

@jlbutler
Copy link
Member Author

Nit, updated the comment for History.Created to describe layer creation time rather than image.

@vbatts
Copy link
Member

vbatts commented Jan 27, 2017

LGTM

Approved with PullApprove

@jonboulle
Copy link
Contributor

jonboulle commented Jan 27, 2017

lgtm

Approved with PullApprove

@jonboulle jonboulle merged commit 72a840e into opencontainers:master Jan 27, 2017
@jlbutler
Copy link
Member Author

This closes issue #517 , I neglected to tag it earlier.

@jlbutler jlbutler deleted the image-spec-517 branch January 30, 2017 13:35
@stevvooe
Copy link
Contributor

@jlbutler Thanks for the contribution!

lucab added a commit to lucab/image-spec that referenced this pull request Apr 3, 2017
PR opencontainers#534 changed Created from string to time.Time field.
This neutered the `omitempty` property on it, as a missing
field is now populated as the default time.Time value.

This commit turns the field into a pointer, in order to keep
the empty-value semantic for `omitempty`.

Fixes opencontainers#626

Signed-off-by: Luca Bruno <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants