Skip to content

0.23.0

Compare
Choose a tag to compare
@oskardudycz oskardudycz released this 08 Jan 14:24
· 23 commits to main since this release

🚀 What's New

1. Finalised the first version of MongoDB event store

Now you can select whether you want to use:

  • single collection,
  • collection per stream or
  • custom collection resolution

That gives the possibility for flexible schema definition. by @oskardudycz in 142, 151.

You can also choose whether you want to provide a connection string and have a MongoDB connection setup automatically or inject and reuse your existing Mongo Client by @oskardudycz in 136, 150

Added sample of Mongodb event store WebApi with Express.js See it here. by @oskardudycz in 157, 158

Added query functions to simplify querying for inline read models You can query get count, etc., without gymnastics directly from the MongoDB event store. by @alex-laycalvert in 139, 147 and @oskardudycz in 160

Added the Mongo inline projection specification. Now you can have integration test for your MongoDB inline projections by @oskardudycz in 161, 163

Added check for the MongoDB projection name uniqueness. That should detect potential issues with multiple projections overriding the same read model accidentally by @oskardudycz in 164

2. Started working on SQLite event store.

It's not yet published, but we already have the table setup and connection handling and the next Pull Requests in the pipeline. Expect the first alpha release soon. by @davecosec in 141, 148, 154, 156.

3. Added idempotence check for Decider Specification

Now you can test command handling idempotence, as described in my blog article by @oskardudycz in #145

4. Updated EvenStoreDB test container to the latest LTS

Now it loads by default 24.10.0 version. by @oskardudycz in 135

5. Added after commit hook to in-memory event store

You can use it to process notifications after events were appended. Note, it's run as in-process, so it gives at-most once processing guarantee. by @oskardudycz in 152

6. Refactored Event type metadata to be explicit

Previously, providing metadata during message creation wasn't required, even if it was defined by type. Now it is. If you don't have metadata, then of course, it's not. by @oskardudycz in 162, 159, 166

📝 What's Changed

  • Adjusted build watch and set explicit build order to adjust the build weird flakiness by @oskardudycz in 167

New Contributors

Full Changelog: 0.22.1...0.23.0