Skip to content

[Question] purpose of eventually-util::optional::Aggregate #160

@danieleades

Description

@danieleades

hi there! I'm just curious what use-case/problem is solved with the eventually-util::optional::Aggregate trait? I have to admit I got a bit confused digging around the codebase by some of the duplicate object names. I think i've got my head around it now!

It seems to me that this trait is meant to be an analogue of the regular Aggregate trait, but that the state may not be seeded until you receive the first event. Is that about right?

Would it be cleaner to simply add a Default trait bound to the Aggregate::State type?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions