Accessing parent navigator

[hakobast]

Our application has bottom nav bar with 2 tabs, to not recreate state every time when tab is switched I'm using the approach mentioned in this release. Everything works fine.

In one of the tabs when button is pressed new screen should be presented in the entire screen instead of inside the tab. To do that I need to access parent navigator. Currently I'm passing it to the child via CircuitContext tags. Tested multiple cases like configuration change, process kill. Everything works fine.

Is it acceptable solution or there are better ones?

[ZacSweers]

Do you need access to the parent navigator or do you just need to signal navigation events up? The latter is more in line with idiomatic compose, and there is a CircuitContent overload that allows passing a lambda to handle child nav events from the calling context.

[ZacSweers]

Sorry you need to be more specific at this point about what you mean by "state"?

[hakobast]

Ah sorry, by state I mean some UI states such as toggle state, input field text, data fetched from network.

[ZacSweers]

Those first two are saveable state handled by compose UI. If you use saveablebackstack those will get managed accordingly. The last one absolutely belongs in your data layer. You can use rememberRetained to cache latest versions in your presenters but the core logic for it should be a higher level.

[hakobast]

Sorry I do not get SaveableBackStack part, your suggestion was to use CircuitContent there is no way to provide to it backstack.

[ZacSweers]

SaveableBackStack also saves all provided values for each record. At this point I think it would be a good exercise to the read to continue this on your own and learn a bit more about how circuit's core components work.