struct MyNavigation<Content>: View where Content: View { @ViewBuilder var content: () -> Content @Environment(.dismiss) private var dismiss var body: some View { NavigationStack(root: content) .navigationBarBackButtonHidden() // .toolbarRole(.editor) .navigationBarItems(leading: CustomBackButton(dismiss: self.dismiss)) } } struct CustomBackButton: View { let dismiss: DismissAction var body: some View { Button { dismiss() } label: { Image(“icon_back”) } } } I […]

My attempt to use navigationStack with navigationPath. Please run this example and note the path.count in the Print statements.
What I am trying to achieve: Passing the navigationPath to child view so that I can use navigationPath.remove.

This creates an intermediate view with text that I must tap to get to my detail v iew. How can I eliminate the middle man and navigate directly to my detail view?

I am in the process of learning Swift, coming from years of PowerShell on Windows, and as I am digging into NavigationStack I am seeing some patterns but I don’t understand what is going on under the hood.

I am coming from 15 years of PowerShell and trying to get my head around this crazy new world of GUI, and running into a problem way to early I fear.
I am working from the AppCoda Navigation Stack post and then trying to implement a router based on Stewart Lynch’s YouTube course on Navigation Stacks. Most things are working, but as I am trying to add a Home button to the toolbar it all falls apart. What I have now (in various files, not shown here, and also not including Previews) is this, and it crashes when I try the home button in the preview and does nothing in the simulator. I am at a loss.

In a basic NavigationStack you get the nice < Title button in the upper left, to take you back to the previous view, and it is automatically named with the .navigationTitle() of that previous view.
You can also have your own toolbar, with say an Info button on the right side like this