Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

mtg: Editors change the decklist

Closed
  • Is something wrong?
#160 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
38/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
typescript
Domain
backend, frontend, full-stack, testing

Research direction

Start with the collaborators module tests named in the acceptance criteria and trace how Editor and Viewer permissions are handled for deck operations. Map each listed edit and owner operation to its authorization checks and the deck page controls. Done means the criteria pass, including proxy handling, role changes on the next request, and the interaction with deck history issue #145; the payload names no specific files or test commands.

Written by the indexing model from the issue text.

Description

ready-for-agent

Parent

#155

What to build

An Editor helps build the deck as a decklist. Editors succeed on every edit operation: deck update (name, description, format), colour identity, bracket, rule zero, advisor settings, and card add, import, update and delete including moving cards between zones. They still see the deck through the Share link redaction, so the proxy flag stays the owner's: an Editor's card update leaves an existing proxy flag untouched, an Editor cannot set it, and new slots an Editor adds are no proxy. Every owner operation stays denied for Editors and answers like a missing deck. Viewers stay read-only.

On the deck page, Editors get the editing controls; owner-only controls (collection, sourcing, drift, Visibility, Share link, Collaborator management, folder, delete) stay hidden.

Deck history (#145 and its tickets): an Editor's edits are Deck changes like the owner's; viewing the Deck history, undo, redo, reset and Deck checkpoints stay owner-only. Whichever of the two features lands second adapts to the other; adjust the glossary wording ("what the owner did") accordingly.

Acceptance criteria

  • An Editor succeeds on every edit operation listed above, import included
  • An Editor's card update leaves an existing proxy flag in place; the proxy flag cannot be set by an Editor; new slots are no proxy
  • An Editor is denied every owner operation
  • A Viewer is still denied every edit operation
  • A level change from Editor to Viewer takes effect on the next request
  • Deck page offers Editors the editing controls and hides the owner-only ones
  • Tests in the collaborators module
Dominant language
TypeScript
Stars
0
Forks
1
Avg merge
10h 20m
Merged PRs (30d)
36

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

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from myOmikron/code

All issues in myOmikron/code

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.