feat(kanban): add "Archive all" action to auto-complete columns#517
Open
reniko wants to merge 2 commits into
Open
feat(kanban): add "Archive all" action to auto-complete columns#517reniko wants to merge 2 commits into
reniko wants to merge 2 commits into
Conversation
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
Adds an "Archive all" button to the header of Kanban columns whose status
has
autoComplete: true. Clicking the button opens a confirmation dialog;on confirm, all cards in that column are archived via the existing
archiveItemserver action.Why
Cards in auto-complete columns are effectively "done" and tend to
accumulate over time. Until now, users had to archive each card
individually — there was no bulk action.
How
KanbanColumnrenders an archive icon-button in the column header,conditional on the column's status having
autoComplete: trueand anonArchiveAllhandler being provided (i.e. the user has edit permission).pass is in flight.
ConfirmModal(destructive variant) with the affectedcolumn name and item count.
Kanban.handleArchiveAlliterates the column's items sequentially,calling the existing
archiveItemserver action for each. The latestreturned checklist state is propagated via
onUpdate, and a finalrefreshChecklist()ensures consistency.before the error; on full failure (zero archived), a plain failure
toast is shown instead.
No new archive mechanism, no header refactor, no changes to the archive
data model.
Why sequential, not Promise.all
archiveItemwrites to the file-based storage; parallel writes againstthe same list file could race. Sequential is the safer default until
the storage layer is shown to handle concurrent writes for a single list.
Testing
ArchivedItemsModalTranslations
enanddewritten by hand.klingonandpirate: in the spirit of the existing strings.Out of scope