Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

mtg: Editors change the decklist

Chiusa
  • Qualcosa non va?
#160 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
38/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
typescript
Ambito
backend, frontend, full-stack, testing

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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
Lingua principale
TypeScript
Stelle
0
Fork
1
Merge medio
10h 20m
PR unite (30g)
36

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di myOmikron/code

Tutte le issue di myOmikron/code

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.