Skip to content

Release v4.2.1
Compare
Choose a tag to compare
@github-actions github-actions released this 19 Jan 09:43
v4.2.1
9a14fb7
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

Summary

Improved consistent behavior for child relationships.
Events that represent something that is related to the same event source id as another event can now be modelled in a projection as a child.

Take the following:

public void Define(IProjectionBuilderFor<Person> builder) => builder
    .From<PersonRegistered>(_ => _
        .Set(m => m.SocialSecurityNumber).To(e => e.SocialSecurityNumber)
        .Set(m => m.FirstName).To(e => e.FirstName)
        .Set(m => m.LastName).To(e => e.LastName))
    .Children(_ => _.PersonalInformation, c => c
        .IdentifiedBy(_ => _.Identifier)
        .From<PersonalInformationRegistered>(_ => _
            .UsingKey(_ => _.Identifier)
            .Set\(m => m.Type).To(e => e.Type)
            .Set\(m => m.Value).To(e => e.Value)));

With the child definition, it will identify the child uniquely based on the IdentifiedBy statement. This tells the engine to use the property Identifier on the target read model / document to identify it.
Within the child definition from statements can now specify a property on the event to be used as the key. The statement UsingKey() accomplishes this. This will then direct the projection engine to use this property to identify the child object and map this with the IdentifiedBy() property on the read model / document.

The point of this all is to be able to share the event source id - being the aggregate identifier for all things related. While the child identifier is the value identifier.

Fixed

  • When ParentKey() is not specified in a child relationship, one can use the UsingKey() to specify a property on the child to be the key that identifies the child.
Assets 2