Question about ComposableArchitecture 2.0

[arnauddorgans]

I saw that onMount reducers will be introduced. Does this mean a reducer will receive onMount automatically when it becomes active in the tree?

I have multiple features composed of child features that do not own views. I need a way to trigger side effects when a reducer becomes alive, even if no view is attached to it.

Today, I handle this by defining a lifeTask action in the root feature. The root manually dispatches lifeTask to all child features. However, for optional child features that are instantiated later, I must explicitly trigger their lifeTask when they are created.

This becomes repetitive and error-prone. It would be much cleaner if onMount were automatically triggered whenever a child feature becomes active in the reducer hierarchy, regardless of whether it has an associated view.

[stephencelis]

Yup, onMount (and onMount(id:)) is not associated with any view. It executes when the feature is first available (or when id changes). For a root store this is when Store is initialized, and for an optional-scoped store when its state becomes non-nil.

[arnauddorgans]

Amazing!