coder13 / coder13/LetsCube

Prevent accidental scramble advancement before competitors are resolved

Aperta
#159 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub
area: rooms bug priority: P1
Lingua principale
JavaScript
Stelle
30
Fork
9
Metriche di merge delle PR
Nessuna PR unita negli ultimi 30g

Descrizione

Rooms should not accidentally generate a new scramble while competing users still need to submit, skip, or be explicitly ignored.

Feedback source:
- Stop rooms from accidentally generating a new scramble when not all competing users have submitted a result.
- Grey out scramble and timer, not just timer.

Acceptance ideas:
- Confirm the server-side condition for advancing scrambles.
- Require every active competitor to have a result, be skipping, be forced-skipped, or no longer be active.
- Make the client UI clearly indicate when the current scramble is no longer available for timing.

Guida per i contributori

Apri la guida per i contributori

Direzione di ricerca

Trace the server-side room logic that advances scrambles, then inspect the client components controlling the scramble and timer. Confirm advancement waits for every active competitor to submit, skip, be force-skipped, or become inactive, and make both controls visibly unavailable when timing cannot continue.

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

Valutazione

Stack tecnologico
javascript, nodejs, react
Ambito
backend, frontend, full-stack
Tipo di issue
Bug
Difficoltà
4/5
Tempo stimato
3-5 giorni
Stato di attività
Tranquilla
Chiarezza
Abbastanza chiara
Idoneità per principianti
55/100

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.