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

Verify store registration consistency across tracing and factory configurations

未关闭
  • 哪里不对？
#608 2 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 7 天内回复

@nmummau 已经在做这个了。

开始于 2026年10月14日。

  • #622 来自 @nmummau —— 未关闭

评估

难度
4/5
预计耗时
3-5 天
新手友好度
48/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
活跃
技术栈
csharp
领域
backend, testing

调研方向

Start with src/Extensions/src/Eventuous.Extensions.DependencyInjection/Registrations/Stores.cs and the dependency injection test project. Read the registration overloads and run the existing registration tests to learn the intended singleton and existing-registration behavior. Add host-level tests using a stateful in-memory store for tracing and factory combinations; done means writes and reads through the registered interfaces share the intended store and the required behaviors are covered.

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

描述

Problem

The store-registration code in Stores.cs has approximately 12% line coverage in the October 5, 2026 .NET 10 coverage run. It contains separate paths for tracing, implementation-type registrations, and factory registrations. You can view a test coverage report I generated here: index.html

A host can build successfully while its reader and writer resolve to different backing stores or its tracing wrappers resolve incorrectly. Registration tests should therefore verify working reads and writes, not just successful service resolution.

Source: Stores.cs.

Proposed tests

  • Build a minimal host using AddEventStore<T> and verify that an event written through IEventWriter can be read through IEventReader and accessed through IEventStore.
  • Exercise both implementation-type and factory registration overloads with tracing enabled and disabled.
  • Verify the corresponding read/write behavior for AddEventReaderWriter<T>.
  • Exercise standalone reader and writer registrations in a working host.
  • Verify singleton and factory-invocation behavior according to the intended contract. Tracing wrappers may be different objects, but must use the intended underlying store.
  • Verify the documented behavior when registrations already exist or registration methods are called more than once.

Acceptance criteria

  • The tracing/registration-overload combinations are covered with actual event writes and reads.
  • Reader, writer, and store interfaces observe consistent backing-store state where registered as one store.
  • Factory invocation counts and service lifetimes match the intended singleton contract.
  • Existing-registration behavior is explicitly tested and documented.
  • Any process-wide diagnostics settings are restored after each test and isolated from parallel tests.
  • Tests use a stateful in-memory store and require no Docker containers.

Validation

Run the dependency-injection test project and collect focused coverage for store registrations. Add a regression test before correcting any inconsistency discovered by the host-level tests.

主要语言
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 摘要。