mtg: Editors use deck-local tags
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
- backend-api-design
Research direction
Start in the collaborators module and read the existing role and tag tests; the issue names no files or test commands. Trace how deck ownership, editor permissions, and tag assignments are handled, then add coverage for the listed Editor and Viewer cases. Done means the acceptance criteria pass, including deck-local tags behaving as the owner's and global tags remaining read-only to Editors.
Written by the indexing model from the issue text.
Description
Parent
#155
What to build
Editors group cards with tags while building. An Editor sees all tags on the deck, global ones included. Create, update and delete only work on deck-local tags of this deck; deck-local tags an Editor creates belong to the deck's owner, so they behave like the owner's own. An Editor can assign and unassign deck-local tags on the deck's cards. Global tags and their card-wide assignments stay owner-only, so an Editor's work cannot change how the owner's other decks are tagged.
On the deck page, Editors get the deck-local tag controls; global tags are shown read-only.
Acceptance criteria
- An Editor sees all tags on the deck, global included
- An Editor can create, update and delete deck-local tags of this deck, and assign and unassign them
- A deck-local tag created by an Editor belongs to the owner and behaves like the owner's own tag
- An Editor is denied creating, changing, deleting, assigning and unassigning global tags, and any deck-local tag of another deck
- A Viewer is denied every tag write
- Deck page shows global tags read-only to Editors
- 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