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

A task's contact cannot be linked, changed or removed after the task is created

Aperta
  • Qualcosa non va?
#266 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
55/100
Tipo di issue
Funzionalità
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
go, graphql, react, sql, typescript
Ambito
backend-api-design, database, frontend, full-stack

Direzione di ricerca

Read TaskScreen.tsx, NewTaskScreen.tsx and operations.ts for the contact field and save flow, then trace UpdateTaskInput through tasks.go, changes.go and the UpdateTask query. Run the named graph and task detail tests to check setting, changing, clearing and preserving a contact when contactId is absent. Done means the task page supports those contact actions with a persistent label, and invalid or cross-tenant contacts are rejected.

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

Descrizione

enhancement help wanted

What happens

The New task form has a "Link a contact" field. The task page has none. A linked contact shows only as a bare link above the Title field, with no label. A task with no contact shows nothing. So you cannot link a contact later, swap it or remove it. On the New task form, the label also goes once a contact is picked.

The graph cannot do it either. UpdateTaskInput has no contactId, task.Changes has no contact, and the UpdateTask query never sets contact_id.

What should happen

The task page shows the contact field after Priority, as the New task form does. With no contact it shows the search. With one, it shows Maria Perez as a link to her contact page and a "Remove Maria Perez" button. The field keeps one visible label in both states, on both screens.

WordPress draws one form for a new page and a saved page. Its Parent field keeps its label, shows None or the parent's title, and lets you search for another page or clear it, before and after the first save.

updateTask takes contactId the way it takes dueTime: absent keeps the contact, null clears it, an id sets it. Save sends it only when it changed, as timeChange does for the time. The resolver reads the contact through the contact store first, so a deleted contact or one from another tenant is refused with a plain error.

A graph test sets, changes and clears the contact, and proves an absent contactId keeps it. Detail tests link, swap and remove a contact.

Where

  • frontend/src/tasks/TaskScreen.tsx, TaskForm and ContactLink
  • frontend/src/tasks/NewTaskScreen.tsx, ContactPicker, moved to its own file
  • frontend/src/index.css, .alphone-tasks__contact and .alphone-tasks__picked
  • frontend/src/tasks/operations.ts, updateTaskMutation
  • graph/schema/tasks.graphqls, UpdateTaskInput
  • internal/graphres/tasks.go, taskChanges
  • internal/task/changes.go, Changes and Apply
  • internal/postgres/queries.sql, UpdateTask
  • internal/graphres/mutations_test.go and frontend/src/test/task-detail.test.tsx
Lingua principale
Go
Stelle
287
Fork
64
Merge medio
13h 3m
PR unite (30g)
66

Preparare l'ambiente

  • Include un Dockerfile o un file Docker Compose
  • Nessun modello di pull request
  • Nessuna guida per i contributori

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 gopherium/AlphOne

Tutte le issue di gopherium/AlphOne

Issue simili

Altre issue su Go

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.