Tasks: board and list as drawn, one-tap state, swipe left, Undo

Chiusa
  • Qualcosa non va?
#346 4 commenti 0 reazioni 1 assegnatario Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

@PelikanFix16 ci sta già lavorando.

Dal 8/10/2026.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
35/100
Tipo di issue
Funzionalità
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
react, typescript
Ambito
accessibility, frontend, testing

Direzione di ricerca

Read the design guide’s §5 and status glyphs, then inspect app/apps/web/src/work/TaskBoard.tsx, ProjectTasks.tsx, and work.css; first review the dependent tokens and shared components in #338 and #344. Rewrite test_tasks_board.py, test_project_state.py, and test_home_tasks.py, then run ./scripts/check_ui.sh and compare both screen sizes and themes against the renders. Done means all four acceptance criteria work, including keyboard and touch interactions, Undo, accessibility, and visual review.

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

Descrizione

agent:ready enhancement

Part of #336 (F-026, founder direction 2026-10-07). Design guide: docs/design/final (§5 behaviour · status glyphs; until #337 merges, read the pinned copy). Interactive boards (light/dark toggle, notes): design canvas, page "Prostota".

Outcome

Tasks are easy to scan and change on both devices.

Final design

desktop-tasks phone-tasks

Acceptance criteria

  • AC-1. The computer board and list and the phone list match the renders: glyph plus word for state, #number, the title, and the owner as a 20 px avatar or Kreska. "Blocked" and "Needs you" are inverted pills.
  • AC-2. One tap on the glyph (or 1–5) changes the state. On the phone, swipe left then Done. Both show a toast with Undo.
  • AC-3. Drag and drop between board columns keeps its keyboard alternative and announces the result.
  • AC-4. The phone Tasks screen has no toolbar besides the view menu in the title and its own filter row, as drawn.

What changes in the code today

From a read of main at 3c553b79; the owner confirms before starting. Paths are under app/apps/web/src, public/ is app/apps/web/public, root scripts/ and tests/ are the repository's, and UI tests are in app/tests/ui.

Change

  • work/TaskBoard.tsx (three columns, drag + "Move to…") and work/ProjectTasks.tsx (Kanban/List radio, search, groups) → the drawn board and list.
  • Status dots ws-dot coloured by --warning/--resolution/--attention (work/work.css) → glyph + word.

Remove

  • Coloured status dots; the Decisions and Results groups (see the Inbox issue).

New

  • One-tap glyph state change and 1–5; swipe left → Done on the phone; Undo toast.

Tests to rewrite

  • test_tasks_board.py, test_project_state.py, test_home_tasks.py.

Depends on

#338, #344 (tokens and shared components first; independent parts can start earlier).

Related: #276 (PR #282) adds the per-project task numbers shown as #number.

How to test

./scripts/check_ui.sh            # browser suite; add the new or changed tests
./scripts/check_application.sh   # when API or data paths change
python3 scripts/check_agent_setup.py && git diff --check

Compare with the renders above at 1440 × 900 and 390 × 844 CSS px, in light and dark, on ./flux demo data, then get an independent visual review with a neutral brief (guide §9). Screenshots do not prove interaction or accessibility, so also test keyboard, touch (Chromium and WebKit emulation), reduced motion and contrast in the running app.

Owner: whoever claims it (assign yourself and comment once). Evaluator: the other agent. The design is a founder direction: implement it as drawn; raise a conflict with a functional contract on #336 instead of changing the design.

Updated 2026-10-07: cross-link to #276 added.

Lingua principale
TypeScript
Stelle
3
Fork
0
Merge medio
18h 21m
PR unite (30g)
385

Preparare l'ambiente

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 ColdPhase/flux

Tutte le issue di ColdPhase/flux

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.