Best way to structure nested deinitializer actions

[PeterKaminski09]

My state is modeled like so:
HomeScreenList > Detail Screen > Component

HomeScreenListState
- var selectedDetailScreenItem: DetailScreenState?

DetailScreenState
- var subcomponentState: ComponentState?

I also have deinitializers set up such that:

• ComponentAction.deinitialize > cancels a long running effect specific to a Component
• DetailScreenAction.deinitialize > cancels a long running effect specific to the entire Details Screen
• HomeScreenListAction.popSelectedItem > because the details screen is presented from a NavigationLink, the reducer handles calls to pop the selected item

Unfortunately, I am running into the dreaded

<Action> was received by an optional reducer when its state was "nil". This is generally considered an application logic error, and can happen for a few reasons:,

To my knowledge, this means that my home screen reducer will now get tightly coupled to ComponentState as I need to deinitialize the components from the bottom up.

This seems to be caused by Effect.concatenate adding effects to a FIFO queue in the store, but what I'd really need is a LIFO stack to uncouple the deinitialization so that effects can be run starting with the bottom most subcomponent moving upwards to the HomeScreenListState

Was just curious if others have found a more elegant way to do this. It's also worth noting I have not had much chance to dig into recent updates to TCA since the 0.16.0 update, so this might have already been solved.