Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Verify store registration consistency across tracing and factory configurations

Aperta
  • Qualcosa non va?
#608 2 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 7 giorni

@nmummau ci sta già lavorando.

Dal 14/10/2026.

  • #622 di @nmummau — aperta

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
48/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
csharp
Ambito
backend, testing

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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.

Lingua principale
C#
Stelle
512
Fork
99
Merge medio
5g 6h
PR unite (30g)
5

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di Eventuous/eventuous

Tutte le issue di Eventuous/eventuous

Issue simili

Altre issue su C#

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.