How to modify AppLifecycleMiddleware to adopt the new MiddlewareProtocol? about swiftrex

[luizmb]

Having a side-effect in the Middleware init is a bad practice. The Middleware Protocol avoids that, because you have to receive an action in order to begin side-effects.

Why is a bad practice? Because you create a Middleware and THEN add it to the Store, so when the .init runs, maybe there's no Store to receive actions, that's why "receiveContext" is called once the store is ready, but at that point you may have lost some callbacks from your side-effects.

To solve that, you need a "bootstrap" action to your middleware, it can be a "Void" or a new case into the Action, but definitely your input action can't be "Never" anymore, every side-effect bootstrap needs to be associated to an input action, and a middleware with Input Action == Never can't perform any task.

This is one of the possible solutions:
npvisual/AppLifecycleMiddleware#2

[haifengkao]

thanks 👏