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

Control events persistence from the domain model

Abierto
  • ¿Algo no está bien?
#82 5 comentarios 1 reacción 0 asignados Ver en GitHub

Los mantenedores suelen responder en 7 días

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
25/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Estancado
Stack tecnológico
csharp
Área
backend, databases

Línea de trabajo

Read the aggregate store and event store paths, then trace how Apply produces Changes and how StreamEvent is persisted. The issue outlines two implementation options: carry archive or truncation information through Changes, or add event class attributes handled by the aggregate store. Done means the domain model can signal persistence to archive or truncate prior events; the issue names no tests, so identify the relevant coverage while tracing these paths.

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

Descripción

enhancement

Right now, the event store is agnostic to what events are being persisted. It is quite a limitation for doing things like #64, domain-driven snapshots, closing periods, etc, as some "fold and archive" or "fold and snapshot" actions need to be controlled by the domain model.

For example, a reservation might get archived after the guest checks out, as the lifecycle of the reservation is done, and it becomes fully immutable (or frozen). Similarly, closing a period would collect the period data in a "new period started" event, and then signal the persistence to truncate all the previous events.

So, the idea is to provide a way for the domain model to tell those things to the aggregate store and further to the event store.

I have two ideas atm:

  • Apply can get an overload or optional parameter to signal the archiving or truncation
  • A set of attributes for event classes to do the same

Both can be implemented at the same time, but the implementation would be in different layers.

  • For Apply the change would be to extend the Changes to contain extra information
  • For attributes, all the work will be done by the aggregate store. The StreamEvent record would need to get new properties.
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.