Repository navigation
feat(web): show versions newest first with dates and a tags table - #47
Merged
Merged
Conversation
Tags and versions were listed alphabetically, so the newest uploads sat at the bottom, and no date was visible anywhere in the tree. Release candidates were mixed with final versions, and the page of an image showed only technical counters. The browse listing takes `sort=recent` (newest first inside components, folders and files, ordered in SQL before the limit so a truncated folder keeps the newest children), and folders and components now carry `lastModified`, the newest upload under them. In the UI the tree defaults to newest first with a Newest/Name switch that is remembered, shows when each entry was uploaded and dims pre-releases. A folder of versions or docker tags opens as a table with filter, sorting, paging, a switch to hide pre-releases and a mark on the newest stable one. The page of a file starts with a summary strip: when it was pushed, its size, the digest with a copy button and the number of pulls.
This file contains hidden or 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
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.
Tags and versions were listed alphabetically, so the newest uploads sat at
the bottom, and no date was visible anywhere in the tree. Release candidates
were mixed with final versions, and the page of an image showed only
technical counters.
The browse listing takes
sort=recent(newest first inside components,folders and files, ordered in SQL before the limit so a truncated folder
keeps the newest children), and folders and components now carry
lastModified, the newest upload under them.In the UI the tree defaults to newest first with a Newest/Name switch that is
remembered, shows when each entry was uploaded and dims pre-releases. A
folder of versions or docker tags opens as a table with filter, sorting,
paging, a switch to hide pre-releases and a mark on the newest stable one.
The page of a file starts with a summary strip: when it was pushed, its size,
the digest with a copy button and the number of pulls.