[Fix #59] image history, use v2 manifest instead of v1 #61
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ds current tag-history call
…story. Better render for created_by
…ve element values rendering Move icons to js mapping function instead of CSS In dockerfile, author cand be randered through `MAINTAINER xxx` or `LABEL maintainer=xxx`
…history-element` - Add id and ExposedPort - Better rendering for arrays - Add more const instead of var
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
A bug was found, when I browse with the browser cache, the tag history does not load because it receives a response with a docker schema v2 and it needs a v1 schema.
What I will do is to use v2 schema instead of v1 (with this, I can use DockerImage object with listeners/triggers).
Moreover, I could make queries savings by passing the DockerImage object directly.
Fixes: #59