Skip to content

feat(ui): rework queue with dedicated views per action type - #63

Merged
antfu merged 4 commits into
mainfrom
antfu/queue-ui-rework
May 28, 2026
Merged

feat(ui): rework queue with dedicated views per action type#63
antfu merged 4 commits into
mainfrom
antfu/queue-ui-rework

Conversation

@antfu

@antfu antfu commented May 28, 2026

Copy link
Copy Markdown
Owner

Summary

The queue UI used to crush every action into a single truncated summary line, hiding most of the data behind ellipses (label colors, avatars, full bodies, merge details, reactions, ifUnchangedSince, source files). This rework gives each entry a card with a colored action pill, a body rendered in the action's natural shape (label pills, user avatars, multi-line text, merge method + commit, emoji + target, etc.), and a footer that opens its source file in the editor. Per-item edits — previously hidden from the queue — are now visible alongside execute.yml / execute.md so every pending op lives in one place. The duplicated row template between panel/Queue.vue and hub/QueueList.vue is gone; both consume a shared QueueEntryCard.

Created with the help of an agent.

Replace the single-line summary row with a card that renders each action's
payload in its native shape: label pills with real colors, user avatars,
multi-line bodies, merge method + commit details, reactions with emoji.
Per-item entries are no longer hidden, and each card's footer opens its
source file in the editor.
@antfu antfu changed the title refactor(ui): rework queue with dedicated views per action type feat(ui): rework queue with dedicated views per action type May 28, 2026
antfu added 3 commits May 28, 2026 13:41
Move the open-source affordance to a small icon button in the header (the
icon already encodes the source type), and drop the dedicated footer.
Surface each entry's issue/PR title next to the number so hub-level
entries are recognisable at a glance.
Show the issue/PR title in the entry card whenever syncState knows it,
not only when the number is being rendered. Adds a regression test that
queue-builder propagates titles from syncState into yml entries.
When navigating between items the `item` computed briefly becomes null
before the v-if/v-else swaps in the empty state. Reka-ui's force-mounted
TabsContent re-rendered children during that window, which crashed
DetailConversationTab on item.author. Guard the tab bodies with v-if="item".
@antfu
antfu merged commit e761168 into main May 28, 2026
5 checks passed
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.

1 participant