Cordy/Cairn
2
1
Fork 0
Code Issues 20 Pull requests Projects Releases Packages Wiki Activity Actions

#244 follow-up: add-peer form inbound Spaces field (v0.6.29) #248

Merged
Cordy merged 3 commits from feat/244-ship4 into main 2026-08-16 11:33:29 +00:00
Conversation 0 Commits 3 Files changed 2 +8 -3
Cordy commented 2026-08-16 11:32:14 +00:00
Owner
Copy link

Closes the last #244 UI gap Nikola found while dogfooding: the "Add a peer" form's "May receive from this peer" section had Users + Groups but no Spaces, even though the card editor and backend already support recvSpaces. Adds the Spaces input + posts receivers.spaces at registration. Frontend-only (backend accepts receivers.spaces since Ship 1).

Closes the last #244 UI gap Nikola found while dogfooding: the "Add a peer" form's "May receive from this peer" section had Users + Groups but no Spaces, even though the card editor and backend already support recvSpaces. Adds the Spaces input + posts receivers.spaces at registration. Frontend-only (backend accepts receivers.spaces since Ship 1).
#244: add-peer form inbound Spaces field (v0.6.29)
All checks were successful
ci / test-and-build (pull_request) Successful in 37s
Details
82d0268c78
Cordy merged commit d90c851767 into main 2026-08-16 11:33:29 +00:00
Cordy deleted branch feat/244-ship4 2026-08-16 11:33:31 +00:00
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: Cordy/Cairn#248
No description provided.
Delete branch "feat/244-ship4"

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?