If I’m using the coordinator pattern as outlined in chapter 23 of the Design Patterns by Tutorials book, how do I go about passing data back through to a parent coordinator from a child coordinator?
Imagine a scenario in which the child coordinator takes care of some lower level preferences that needs to propagate back to the parent so that it could be passed down to an alternative sibling route – in my specific use case I have an App Coordinator that manages Onboarding- and Home Coordinators. During the Onboarding process the user is asked for their in-app upgrade preferences which needs to be passed to the sibling Home Coordinator, both of which are managed by the App Coordinator.
I’ve thought about passing a general purpose dictionary back through the dismissal process which can be part of the dismissal closures, but wasn’t able to make this work. Any suggestions on how to best handle this?