Repository navigation
Conversation
woolsen
force-pushed
the
feat/container-created-at-sort
branch
from
October 20, 2026 13:36
ce9eb1f to
fcb795c
Compare
3 tasks done
woolsen
force-pushed
the
feat/container-created-at-sort
branch
2 times, most recently
from
October 20, 2026 13:38
a2a564b to
a9c72b2
Compare
Add a creation time column to the container list. The column uses the backend createdAt order field and displays the existing createTime value. It follows the standard three-state sort cycle, starting with newest first.
woolsen
force-pushed
the
feat/container-created-at-sort
branch
from
October 20, 2026 13:50
a9c72b2 to
281789e
Compare
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.
What this PR does / why we need it?
The container list can only be sorted by name. Add a creation time column so containers can also be ordered by when they were created, without changing the default sort (
nameascending).Depends on #14140: the third click (cleared state) restores the default order only after that PR is merged.
Summary of your change
createTimevalue and uses the backendcreatedAtorder field directly through the column prop.nameascending).Verification
npm run build:devpasses.orderBy=createdAt, order=descending;orderBy=createdAt, order=ascending;orderBy=name, order=ascending(with fix(container): reset sort to default when cleared #14140);createTimevalues.Please indicate you've done the following: