Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

arch: IIncidentSession/IUiDispatcher/ITrustStore live in LageBuch.Sync; collapse the 5-file-per-operation session ceremony

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

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
35/100
Issue 类型
重构
描述清晰度
基本清楚
活跃度
活跃
技术栈
csharp
领域
backend

调研方向

Start with the architecture review and inspect src/LageBuch.Sync/IIncidentSession.cs, LocalIncidentSession, RemoteIncidentSession, SyncCommand, and CommandApplier; the issue names no file paths for the latter four. Trace how view-models and the host apply commands, then assess the proposed interface move and session consolidation. Done means the session abstractions are owned by AppLogic or a contracts project and the local/remote operation surface is consolidated as described.

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

描述

enhancement

From the 2026-09-09 architecture review of main (35d86e1). Related: the "Local/Remote session lockstep" item still open in #167.

IIncidentSession (src/LageBuch.Sync/IIncidentSession.cs:22), the application layer's primary port that every view-model drives, lives in LageBuch.Sync together with IUiDispatcher and ITrustStore. AppLogic therefore depends on the sync assembly for its core abstraction, and LocalIncidentSession (in AppLogic) implements an interface owned by Sync.

Adding one domain operation today touches five files: the interface, the LocalIncidentSession forwarder, the RemoteIncidentSession forwarder, a SyncCommand record and a CommandApplier case.

Proposal

  1. Move IIncidentSession, IUiDispatcher and ITrustStore to AppLogic (or a LageBuch.Contracts project); Sync implements them.
  2. Collapse the session surface: let LocalIncidentSession apply SyncCommands through CommandApplier exactly as the host does, so the interface becomes Apply(SyncCommand) plus the three file operations and the lifecycle members. View-models then construct commands, and the local/remote split is one method instead of ~40.
主要语言
C#
星标
1
派生
3
平均合并
4 小时 15 分钟
30 天内合并 PR
181

环境准备

从这里开始

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

CodeForFire/lagebuch 的其他 Issue

查看 CodeForFire/lagebuch 的全部 Issue

相似的 Issue

更多 C# Issue

把新 issue 发到你的邮箱

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