John Patrick Morgan

Note: #51 includes details of a potential rewrite of the library that should help break down flows between different modules without these limitations.

Thanks @ChaosCoder for giving this problem your thought. I think the idea could be made to work, but I don't think it would be a small change, as there are...

Hi @toanbv-fabbi, thanks for your question. There's been a [little discussion](https://github.com/johnpatrickmorgan/FlowStacks/issues/21#issuecomment-1103213347) of this previously: I'd really like to provide a nice API for switching out the current view with a...

@bbernberg Thanks a lot for the suggestion! I think giving users the option to use `NavigationStack` on iOS 16 and above would be a useful feature in other ways too.

@ivarvanwooning I'm afraid not. As this affects vanilla SwiftUI (whenever a NavigationLink is removed from the view tree due to popping multiple screens), I can't do much beyond filing a...

In the latest release (v0.8.0), you can add `.nbUseNavigationStack(.whenAvailable)` anywhere outside your `NBNavigationStack` so that the library will use `NavigationStack` under the hood instead of `NavigationView`, which avoids these annoying...

Sorry for the radio silence on this issue. I've been working on a slightly different implementation that would overcome the drawbacks that @strangeliu mentioned (thanks for your work on this...

I've raised a PR #28, attempting to overcome the limitations @strangeliu described here. The API more closely resembles that of NavigationSplitView, in that you can have two or three pane...

I'm still not too clear what issue this PR addresses, so I'll close it for now.

No update so far on the feedback I'm afraid ([FB11490806](https://openradar.appspot.com/FB11490806)). I'll close this PR as it doesn't solve the issue sadly.