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

Split persisted and domain events

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

维护者通常 7 天内回复

还没有人认领这个 Issue。

评估

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

调研方向

Start by reading the event mapping approach in issue #82 and trace how Eventuous currently maps and persists events. The proposed change is optional two-way mapping, with unmapped event types passing through; done means domain and persisted events can be mapped independently while preserving that pass-through behavior. The issue names no files or tests.

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

描述

enhancement linear

For a while, I advocated treating events as contracts and keeping them clean of sophisticated types like value objects.

It solves the issue of serialisation as it should work unconditionally, but it introduces some issues:

  • Repeated wrapping and unwrapping of value objects in the aggregate and the state code
  • Applying mapping attributes (which are infrastructure-oriented) to domain events
  • Lack of persistence control from the domain model side (I might not want to persist all the events)

Similar to #82, it is possible to map persisted events to domain events (and back) to separate those concerns.

Here's the idea:

  • Add an optional two-way mapping
  • Treat it as an addition, meaning look inside the map first and pass through unmapped types

EVE-42

主要语言
C#
星标
512
派生
99
平均合并
5 天 6 小时
30 天内合并 PR
5

环境准备

  • 提供 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

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

Eventuous/eventuous 的其他 Issue

查看 Eventuous/eventuous 的全部 Issue

相似的 Issue

更多 C# Issue

把新 issue 发到你的邮箱

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