v0.2.2 - Minor enhancements

• When an aggregate is loaded and not found, the system now returns ErrAggregateNotFound. This makes it easier to identify and handle this error within your codebase.
• Implemented a minor fix to address an issue that could occasionally block a transaction.

Release v0.2.1 - Documentation Update and Improvements

We're excited to announce the release of v0.2.1 for our Event Sourcing Library. This update focuses on enhancing our documentation to help users better understand how to implement event sourcing in their applications.

What's New in v0.2.1:

• Enhanced Documentation: Added comprehensive usage examples in the README.md to guide you through defining your own aggregate states and event states, creating and applying events to aggregates, and storing them efficiently.

As always, we welcome your feedback and contributions to help make our library even better.

Getting Started with v0.2.1:

To get started with v0.2.1, visit our GitHub repository and follow the updated instructions in the README.md. Don't forget to check out our Event Sourcing To-Do Example for a hands-on demonstration of how to implement the library in a real-world application.

Full Changelog: v0.2.0...v0.2.1

v0.2.0 - Customizable Storage Naming with StorageNamer Interface

What's New in v0.2.0

Introducing the StorageNamer Interface

This release marks an important milestone for our library with the introduction of the StorageNamer interface. This new feature is aimed at enhancing the way aggregates are tied to their storage entities.

Key Features:

• Customizable Storage Entity Naming: Aggregates can now define their corresponding storage entities more explicitly. This allows for better adaptability to different storage backends and user needs.
• Improved Scalability: The StorageNamer interface brings a more scalable approach to handling storage naming conventions.
• Backward Compatibility: The implementation of StorageNamer is optional. If an aggregate state does not implement StorageNamer, the library will default to using the aggregate state's type as the storage identifier, ensuring compatibility with existing codebases.

Other Improvements

• Updated documentation to include StorageNamer usage and examples.

Notes for Developers

• Please review the updated documentation for guidance on implementing the StorageNamer interface in your projects.
• We encourage feedback and contributions to further improve this feature.

We are excited to see how this new release will help in your development processes and look forward to your valuable input.

---

Thank you for using our library, and we hope you find these new features beneficial!

v0.1.0

Includes postgres storage tests.