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

未关闭
#806 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
45/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
electron, typescript
领域
desktop

调研方向

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.

由索引模型根据 Issue 内容生成。

描述

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.
主要语言
TypeScript
星标
3
派生
0
平均合并
17 小时 33 分钟
30 天内合并 PR
163

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

musterhq/muster-code 的其他 Issue

查看 musterhq/muster-code 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。