Daniel Peter

I think we need to update TCA in the example project to get this to pass on CI. Could you `Update to latest package versions` in the workspace and commit...

https://github.com/Bahn-X/swift-composable-navigator/runs/4085428175?check_suite_focus=true#step:5:86 According to the looks, CI uses 0.28.1 as well. I'll check later tonight why CI fails (in roughly 3 hours), my first assumption was wrong, sorry!

Ah, thanks for investigating! Guess it's time to bump CI to Xcode 13. 🙈

Did you try an onDismiss PathBuilder? https://github.com/Bahn-X/swift-composable-navigator/blob/main/Sources/ComposableNavigator/PathBuilder/PathBuilders/PathBuilder+OnDismiss.swift I think, that's what you're looking for. It it isn't, let me know. :)

You could subscribe to the datasource path publisher and diff on it. There is no guarantee that only a single screen is dismissed at a time (going back to a...

Hm, interesting. I will look into this. 🧐

@krzysztofzablocki Thanks! This is next up after providers (a StateObject for iOS13 applications). I had a couple of ideas how to approach this: # 1. Active navigation path stays linear...

Timeline for this: I'm pretty busy this week and will probably not find any time to work on this, but will try to make some room for this feature next...

> Outside of TabBar will this API design also cover the situation where the user can have multi-column navigation design that can be found on some Apps (iPad / Mac),...

I started looking into this today. ```swift struct SomeTabbedView: View { var body: some View { TabView( selection: .constant(1), content: { Text("Tab Content 1").tabItem { Text("Tab Label 1") }.tag(1) Text("Tab...