Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Verify store registration consistency across tracing and factory configurations

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

Los mantenedores suelen responder en 7 días

@nmummau ya está trabajando en esto.

Desde el 14/10/2026.

  • #622 de @nmummau — abierto

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
48/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
csharp
Área
backend, testing

Línea de trabajo

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.

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

Descripción

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.

Lenguaje dominante
C#
Estrellas
512
Forks
99
Merge medio
5 d 6 h
PR fusionados (30 d)
5

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 Eventuous/eventuous

Todos los issues de Eventuous/eventuous

Issues similares

Más issues de C#

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.