Change a post's requests afterwards; lock a thread (#292) #306
No reviewers
Labels
No labels
area/ci
area/desktop
area/packaging
area/protocol
area/reading
area/ui
area/web
area/writing
kind/bug
kind/feature
kind/infra
kind/request
needs/user
parked
perf
security
upstream
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
littlefox/neokom!306
Loading…
Reference in a new issue
No description provided.
Delete branch "issue-292-lock"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Closes #292
An author changes a post's requests after writing it (#292, roadmap "Protocol gaps"):
Kom::set_requestandKom::remove_aux, onemodify-text-info[92] each; the server decides who may (author or supervisor);Verified: devserver integration test
change_requests_afterwards(lock, unlock, read confirmation on/off, remove a cross-reference; another person refused); newe2e/tests/lock.spec.ts(lock → field gone, "Låst för svar"; unlock → back; read confirmation on/off) in desktop/android/iphone; full e2e suite 375 passed (2 flaky on retry, unrelated: channel-window, soak); lint with CI's three clippy commands.🤖 Generated with Claude Code
https://claude.ai/code/session_01XJW2ocwLunyaLiUwCBHEP8