Settings to sort repositories and images in Registries view

[michalpokusa]

Would it be possible to add a setting that makes it possible to sort images on remote registry?

Similar settings already exist for Images, Networks, Volumes etc. thus it seems like a logical complement.

I suggest adding the following settings:

with options:

• MostRecentPush - e.g. repo "a" has image tag from 1 week ago and repo "b" has image tag from 1 day ago, the the order would be "b", "a" etc.
• Label (default) - always with respect to the name, so "a", "b" etc.

---

with options:

• CreatedTime - repo "a" has tags "1.2.3" (3 days ago), "new-feature" (1 day ago), "latest" (2 days ago), then the order would be "new-feature", "latest", "1.2.3"
  (this one will probably be the most usefull one)
• Label (default) - repo "a" has tags "awesome-feature", "1.2.3", "latest", then the order would be "1.2.3", "awesome-feature", "latest"
• LatestThenLabel - repo "a" has tags "awesome-feature", "1.2.3", "latest", then the order would be "latest", "1.2.3", "awesome-feature"
  (this might be useful when one uses commit hash as image tag, so the latest wont be sorted somewhere in the middle)
• Size - repo "a" has tags "1.2.3-some-release" 100MB and "1.2.4-new-feature" 125MB, then the order would be "1.2.4-new-feature", "1.2.3-some-release"

If any two repositories/images have to same property they are sorted by, every option might fallback to alphabetic order.

Thanks for all the work on this extension, I use it extensively and it is extremely helpful in every-day tasks. 😃

[bwateratmsft]

Hm...due to the way that the last-updated-date is fetched (async, in parallel, after-the-fact, because it requires a web request for each individual image), this would be difficult. It would certainly mean degraded performance when sorting by last-updated-date.