Skip to content

feat(memory): delete a list with stack memory list delete - #199

Merged
arthware-dev merged 3 commits into
feature/rc2from
feat/list-delete
Oct 12, 2026
Merged

arthware-dev merged 3 commits into
feature/rc2from
feat/list-delete

Conversation

@arthware-dev

Copy link
Copy Markdown
Contributor

Summary

  • stack memory list delete <list> --as <person> removes a list nobody needs. A list with open items is refused with the items named unless --yes is given; the archive stays.
  • Stacky deletes a list when asked, and asks first when it still has open items. Before, it emptied the list item by item and explained that the page could not be removed.
  • Deletion goes through the same Forgejo read-modify-write as every list change: a transform answering None deletes the file, authored by the person.

Refs: #194

Test added 3 commits October 12, 2026 18:15
A list nobody needs any more could only be emptied item by item, which
left an empty page behind in the wiki and in every list overview.

`stack memory list delete <list> --as <person>` removes the list in one
commit authored by that person. A list that still has open items is
refused with those items named, unless `--yes` is given, so whoever
asked can be asked whether they go too. The list's archive stays: it is
the record of what was bought, and a list started again under the same
name finds its known items there.

The Forgejo read-modify-write now deletes the file when the transform
answers `None`, against the hash it was read at, so a deletion goes
through the same write path as every other list change.
The move from `todos.md` to lists read a file's hash with `.get`, which
the type checker reads as possibly `None` where the file change wants a
string. Forgejo always answers with a hash for a file it returned.

No behaviour change.
"We don't need the hardware store list any more" made Stacky remove
every item one by one, and then explain that the page itself could not
be removed.

`list_edit` gains `op=delete`. The store refuses a list with open items,
naming them, and Stacky asks the person; only their yes sends
`confirmed`, which becomes `--yes`. The user guide says how.
@arthware-dev
arthware-dev merged commit 1e0d216 into feature/rc2 Oct 12, 2026
1 check passed
@arthware-dev
arthware-dev deleted the feat/list-delete branch October 12, 2026 16:38
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