#603: OCM sharing joins the share panel as a federated addressee #608
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "fix-603"
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 mockup batch A rev 2 blocks 4–5. Merged tagged picker over OCM contacts (pure
fed-matchesblock, #552 rule: only established contacts), boundary notice before confirm, Add branches to the existing OCM share endpoint with role→perms, My shares lists outbound federated shares (grant < fed < link ordering inshare-groups) with Federated badge + working revoke. Interim free-text section, css kill-switch, handler and dead i18n keys removed. i18n ×4. Red witnessed, green 29/29 + fence gate.The recipient picker offers established OCM contacts alongside local people and groups (rows tagged Federated with the host); picking one surfaces the boundary notice and Add creates the OCM share through the existing endpoint with the panel's role mapped to perms. My shares lists outbound federated shares between grants and links, with the host, a Federated badge, the role, and a working revoke via /api/v1/ocm/shares/out/{id}/end. The interim free-text federated address row, its css kill-switch, its handler and its dead i18n keys are removed. i18n x4; pure blocks fed-matches (new) and share-groups (ordering) carry the logic; the shares-view harness gains the feat dependency.