Reusable flows in different coordinators

[TiagoSantosSilva]

Hello,

So I'm currently developing an app where I have 2 screens that I call NamingFlow, these screens allow the user to either insert or update their name on the first screen, and the second one is a success/completion screen.

I created a coordinator for it, leaving me with:

• NamingFlowCoordinator (contains NavigationStack with NamingFlowStepA being the root)
• NamingFlowStepA
• NamingFlowStepB

I want to use this flow in 2 different places of my app, namely the Onboarding and the Account parts.

On my Onboarding flow I already have a coordinator with a NavigationStack also, same for the Account flow.

The issue I'm currently facing is that I want to display my Naming low in both of the other flows but I'm only able to do so through a Sheet and not through a Push (path.append(...)). If I try to do it the app crashes - think that's because usually one is not able to push a navigation controller into another navigation controller.

Would there be a way for me to achieve what I want so that I'm still able to reuse the NamingFlow as a whole instead of having to discard the NamingFlowCoordinator and instead independently navigate into NamingFlowScreenStepA and NamingFlowScreenStepB and with these navigations having to be handled inside each of the calling Coordinators/NavigationStacks (Onboarding/Account)?

So what I'm currently trying to achieve is

On OnboardingCoordinator

struct OnboardingCoordinatorFeature {
struct State {...}
enum Action {...}

struct Path {}
enum State {
case onboardingStepA
case onboardingStepB
case onboardingStepC
case namingFlowCoordinator
}
}

instead of

struct OnboardingCoordinatorFeature {
struct State {...}
enum Action {...}

struct Path {}
enum State {
case onboardingStepA
case onboardingStepB
case onboardingStepC
case namingFlowStepA
case namingFlowStepB
}
}

Same for the AccountCoordinator.

Sorry if this sounded confusing. Thank you so much for your help in advance.