Global Stepper implementation about rxflow HOT 4 CLOSED

@TobiasRe please make an issue or talk about the memory issues

from rxflow.

Thanks @twittemb

Yes the CompositeStepper helps, if I including navigation to the corresponding sub flows in my MainFlow.
The issue that remains is how to handle deep linking on app start. Especially if the app needs some kind of bootstrapping/login before the app is ready to handle the deep link.

I guess the best to create an Observable where the deep link step is queued until the app is ready.

let deepLinkObservable = deepLinkSteps.sample(mainStepper.steps.filter{$0 == AppSteps.ready})
deepLinkObsersavable.subscribe(onNext: {step in 
    deepLinkStepper.accept(step)
}).disposed(by: disposeBag)

or similar.

from rxflow.

This feature is currently on hold for me.
There are serious memory management issues with RxFlow to fix first.

I can create a PR when the Deeplink Stepper implementation is done.
Let's close this for now.

from rxflow.

Hi @TobiasRe

Thanks for your feedback.

I think you could use the new "CompositeStepper" feature. In your AppDelegate you could something like that (adapt to your case of course)

let deepLinkStepper = DeepLinkStepper()
let mainStepper = CompositeStepper(steppers: [OneStepper(withSingleStep: DemoStep.apiKey), deepLinkStepper])
 coordinator.coordinate(flow: mainFlow, withStepper: mainStepper)

DeepLinkStepper should be a custom Stepper that you have to write (just implement the Stepper protocol).

You will trigger your instance of deepLinkStepper when a notification is received (DeepLinkStepper can have a function per notification type for instance). As it is associated to the MainFlow, Steps triggered by the DeepLinkStepper will be catched in that flow and you just have to implement the navigation in the switch statement of the navigate(to:) function.

Does it fit with your needs ?

from rxflow.