0.32.0
🚀 What's New
- Added message type to store events, commands, and unify message processing. It adds a Message type that's either a command or an event. I added an additional property called kind, which will inform you what the message actually is (so if it's an event or command). This is the first step in enabling message storage and workflows. Kind is not mandatory, it's just a rebranded flavour type we already had. by @oskardudycz in 183
📝 What's Changed
- BREAKING: Renamed events tables to messages in the PostgreSQL and SQLite schemas and added message kind column. This is in theory breaking change, but I added automated migration script for PostgreSQL schema that should handle it seamlessly. If you faced any issues with that, please send us an info on Discord channel and we'll help in that by @oskardudycz in 184
📚 Docs
- Added overview page to documentation See it live in documentation by @tburny in 200
- Improved samples of events with metadata by @shraddha38 in 201
New Contributors
- @shraddha38 made their first contribution in 201
💬 Discuss this release on Discord
Full Changelog: 0.31.0...0.32.0