Change a post's requests afterwards: lock a thread for replies #292
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#292
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
Approved for 0.7 (D-063). It's in the roadmap's "Protocol gaps".
Let an author change a post's requests after it's written:
The call is
modify-text-info[92], which adds and removes aux items. The server decides who may do it (the author, or a supervisor).Tests: integration against the devserver; e2e for locking a thread and the reply field disappearing.
Merged in #306; main green as of run #533 (after #305). Verified: devserver integration test change_requests_afterwards (lock, unlock, read confirmation, remove a cross-reference; another person refused); e2e lock.spec (lock → reply field gone and 'Låst för svar'; unlock → back; read confirmation on/off) in desktop/android/iphone; full e2e suite; lint with CI's three clippy commands.