This release introduces a more flexible and powerful mechanism for managing dispatch events with new strategies for merging intervals, enhanced customization options, and better overall alignment with evolving SDK dependencies. It also simplifies actor initialization while maintaining robust support for diverse dispatch scenarios.
- Two properties have been replaced by methods that require a type as parameter.
Dispatcher.lifecycle_eventshas been replaced by the methodDispatcher.new_lifecycle_events_receiver(self, dispatch_type: str).Dispatcher.running_status_changehas been replaced by the methodDispatcher.new_running_state_event_receiver(self, dispatch_type: str, unify_running_intervals: bool).
- The managing actor constructor no longer requires the
dispatch_typeparameter. Instead you're expected to pass the type to the new-receiver function. - The
DispatchManagingActorclass has been renamed toDispatchActorsService.- It's interface has been simplified and now only requires an actor factory and a running status receiver.
- It only supports a single actor at a time now.
- Refer to the updated usage example for more information.
DispatchUpdatewas renamed toDispatchInfo.
- The SDK dependency was widened to allow versions up to (excluding) v1.0.0-rc1600.