mtg: "Shared with me", leaving a deck and the Collaborator list
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- typescript
- Domain
- full-stack
Research direction
Start with the collaborators module and its tests, then trace the deck list API and deck list and deck page entry points named in the acceptance criteria. Check how shared access and collaborator levels are represented, and follow the project’s i18n and spec/client generation workflow. Done when collaborators can find and leave shared decks, view the read-only collaborator list, and the listed access rules pass the module tests.
Written by the indexing model from the issue text.
Description
Parent
#155
What to build
Collaborators find shared decks without a link and can leave them. The deck list gets a "Shared with me" section holding the decks the Account collaborates on, with the owner's username and the caller's level. Shared decks are never filed into folders (folders stay the owner's). Any Collaborator can read the deck's Collaborator list (who and at which level), shown read-only on the deck page, and can leave the deck at any time from the deck list or the deck page.
Acceptance criteria
- The deck list API returns the decks shared with the caller, with owner username and level, separate from the caller's own decks and folders
- Deck list page shows a "Shared with me" section with a "Leave" action
- Any Collaborator can read the Collaborator list of the deck; non-collaborators get the missing-deck answer
- Deck page shows Collaborators a read-only Collaborator list
- Leaving removes the deck from "Shared with me" and its access on the next request; the owner cannot "leave" their own deck
- A level change by the owner shows up in "Shared with me" on the next request
- Access survives a Rename of the owner or the Collaborator
- New strings via i18n; spec and client regenerated; tests in the collaborators module
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 1
- Avg merge
- 10h 56m
- Merged PRs (30d)
- 34
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from myOmikron/code
-
wayfinder:task
Difficulty 1/5 Under an hour Newbie friendliness 90/100
Maintainers usually reply within 1 day
-
wayfinder:task
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
myOmikron/code#102 · 2 comments ·
Maintainers usually reply within 1 day
-
ready-for-agent
Difficulty 5/5 Over a week Newbie friendliness 18/100
Maintainers usually reply within 1 day
-
needs-triage
Difficulty 5/5 Over a week Newbie friendliness 25/100
Maintainers usually reply within 1 day
-
needs-triage
Difficulty 5/5 Over a week Newbie friendliness 25/100
Maintainers usually reply within 1 day
Similar issues
-
native
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
prime-radiant-inc/evener#4839 ·
Maintainers usually reply within 1 day
-
bug needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
processone/fluux-messenger#1790 ·
Maintainers usually reply within 1 day
-
🛣️ Infrastructure
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
opencrvs/opencrvs-core#14232 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
kunchenguid/gh-axi#220 ·
Maintainers usually reply within 1 day