Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Finishing an entire flow #14

Open
chrsp opened this issue Dec 7, 2020 · 0 comments
Open

Finishing an entire flow #14

chrsp opened this issue Dec 7, 2020 · 0 comments

Comments

@chrsp
Copy link

chrsp commented Dec 7, 2020

Hi. I'm using this Coordinators idea in my projects and have a issue here regarding to memory management. Imagine that I started a specific flow: the Login flow. This flow has 3 screens, and after the login is completed I go to the home screen. When I'm in the home screen I want to free all the Login flow screens from the memory. How to do that? One thing I tried to do was to go in the first Login screen coordinator and emitting an onNext event, so it should be disposed. However, it isn't being disposed. Another problem is: for this cases I have to not only all be concerned about releasing the coordinator, but to removing the controllers from the navigationController. I think the best way to do that was to be able to, in this case, when I'm starting a new flow, like the home flow, I should be able to simply starting it from the strath ignoring the previous one, that should be automatically released. Some way I can do that in the current structure?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant