0.17.1 Bugfix Release

Fixed

• #91 ImmutableRecord VOs inside arrays are not converted
• ReadModelProxy not initialized when resetting

0.17 Dev Release

Changed

• #99 : Revert custom messages support (Read PR description for details)

0.16.1 Bgufix Release

Fixed

• #98

0.16 Dev Release

Update: It is highly recommended to not use this release but the newer v0.17 release instead! Custom message support was removed again so DO NOT rely on that feature!

Added

• #93: Immediate Consistency Mode
• DeletableState interface
• #92 Custom Message Support

Changed

Fixed

• #96 : Fixed bug where fromInt would be called on a VO that has fromFloat
• FloatType type hints
• Fix null handling of EqFilter

0.15 Dev Release

Added

• #88 : AR function can yield additional event metadata

0.14 OpenAPI/Swagger Integration

This dev release is the first one without GraphQL support

See #84 and #4 for details.

Internal Event Machine handling did not change much but a few changes were made:

• no GraphQL server integration
• $eventMachine->registerInputType() is removed, because we no longer need to differentiate between return and input types. This was a GraphQL limitation

The tutorial is updated as well.

0.13 Dev Release

We switched back from alpha releases to dev releases!

After collecting user feedback we decided to move some parts out of event machine including GraphQL integration!

We want to focus on an extendable core and integrate the event-store-mgmt-ui

This release marks the new development phase with an upgrade to support PSR-15, see #83

v1.0-alpha.7 Release

Fixes

• #81 Include type definitions in JSON Schema validation

v1.0-alpha.6 Release

Changed

• #78 BC BREAK! :
  • QueryDescription::queryComplexity removed
  • QueryDescription::returnType renamed to QueryDescription::setReturnType

Info

We decided to remove GraphQL Integration. The reason for this is that we want to make use of the full power of JSON Schema in Event Machine but if you do that you can no longer translate JSON Schema to GraphQL. The idea is to use the JSON Schema as API documentation and build a frontend app that can read the schema and generate a documentation along with an editor to send messages to the backend and view the results (in case of queries).
Progress is tracked in the PR: #84

1.0-alpha.5 Release

Fixed

• Aggregate state not loaded if custom stream name is used