From c6561f9bfb040c672dcb33966ec35fc5a28f985e Mon Sep 17 00:00:00 2001 From: Freek Van der Herten Date: Fri, 20 Sep 2019 10:56:16 +0200 Subject: [PATCH] Update UPGRADING.md --- UPGRADING.md | 21 +++++++++++++++------ 1 file changed, 15 insertions(+), 6 deletions(-) diff --git a/UPGRADING.md b/UPGRADING.md index b65cea2..3d3ab38 100644 --- a/UPGRADING.md +++ b/UPGRADING.md @@ -2,16 +2,25 @@ Because there are many breaking changes we cannot give you a waterproof list of steps to provide. There are many edge cases this guide does not cover. We accept PRs to improve this guide. -## From v1 to v2 -- Add a nullable `aggregate_uuid` field in the `stored_events` table -- Delete the `projector_statuses` table -- Remove all options in the config file not present in the config file that ships with v2 -- In v1 streams were used to track if events came in the right order. All support for event streams has been removed. If for your projectors the order of events is imports, use a queued projector. -- v1 tracked which events were already processed by a given event handler. In v2 all functionality around projector statusses is removed. It's now your own resposibility that you give all projectors the right events. +## From laravel-event-projector to laravel-event-sourcing + +The laravel-event-projector package has been renamed to laravel-event-sourcing. Upgrading from v3 of laravel-event-projector to laravel-event-sourcing is easy. Take a look in [the upgrade guide for laravel-event-sourcing](https://github.com/spatie/laravel-event-sourcing/blob/master/UPGRADING.md). + + + ## From v2 to v3 - Add a `stored_event_repository` config key with the following value: `\Spatie\EventProjector\EloquentStoredEventRepository::class` - If you're using a different model for event storage: 1. Make sure the model extends `\Spatie\EventProjector\Models\EloquentStoredEvent` + + +## From v1 to v2 + +- Add a nullable `aggregate_uuid` field in the `stored_events` table +- Delete the `projector_statuses` table +- Remove all options in the config file not present in the config file that ships with v2 +- In v1 streams were used to track if events came in the right order. All support for event streams has been removed. If for your projectors the order of events is imports, use a queued projector. +- v1 tracked which events were already processed by a given event handler. In v2 all functionality around projector statusses is removed. It's now your own resposibility that you give all projectors the right events.