Projects, Roster and Inbox: sync tasks, runs and the Inbox from every connected Muster Server at once

Abierto
  • ¿Algo no está bien?
#806 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
45/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
electron, typescript
Área
desktop

Línea de trabajo

Start from runtime/domains/paperclip.ts, where the single-server sync pipeline (OrgReader, live socket, writes) lives. Read #803 and spec clause 13 to learn the current connection model. Write workflow tests for two-server sync first (red), then merge one reader per server into a tagged snapshot. Done when acceptance criteria 1-4 pass: both servers' rows show labelled and writes route to source.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

type:feature

Follow-up to #803 (part of #146 / #147).

After #803, Settings › Integrations holds many Muster Servers side by side. Projects and orgs are read from every connected server at once and labelled with their server. Tasks-as-chats, Roster, Inbox, Ledger, runs, routines, approvals and the live socket still sync from one server at a time: the one marked "Projects, Roster and Inbox sync from this server" in the list, changed with Use for Projects.

That sync is one pipeline in runtime/domains/paperclip.ts: one backend, one org read (built), one live socket and session, one write path, and orgs.*/check-out on that connection. Merging it across servers means:

  • one OrgReader and live socket per connected server, merged into one snapshot with every row tagged by server;
  • writes (comment, status, assign, approve, cancel run, Work locally) routed to the server the row came from;
  • the Inbox and badge counting items from every server;
  • approvals carried over by an import decidable on the server they came from, not only the synced one (linkedApproval);
  • a browser-session cookie for a server that is not the synced one kept for that server (today it waits on the synced connection).

Acceptance (spec clause 13, workflow tests red first):

  1. With two servers connected, tasks, agents, runs and Inbox items from both show at once, each labelled with its server.
  2. Acting on a row writes only to its own server.
  3. One server going offline shows its rows as offline and leaves the other's live.
  4. No "Use for Projects" choice is needed any more; it is removed.
Lenguaje dominante
TypeScript
Estrellas
3
Forks
0
Merge medio
17 h 33 min
PR fusionados (30 d)
163

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de musterhq/muster-code

Todos los issues de musterhq/muster-code

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.