Basic List Navigation (iOS 14) and some CRUD

[tylerjames]

I am a super-noob when it comes to SwiftUI but I've been using TCA with UIKit for a little while. I'm trying to get a bit of experience with SwiftUI so I'm remaking some simple features.

I have a list of saved network credentials (SavedNetwork) each list item is a navigation link that goes to a NetworkDetailView that displays some info and also contains a Delete button to delete the network.

For this basic navigation scenario I have something like this:

WithViewStore(store) { viewStore in
  List {
    ForEachStore(
      store.scope(state: \.networks,
                  action: SavedNetworks.Action.networkDetailsAction(id:action:)))
    { network in
      NavigationLink(
        destination: NetworkDetailView(store: network))
      {
        Text(ViewStore(network).name)// This viewstore part feels like a hack to get to the network name
      }
    }
  }
}

Is that right? In the Navigate and Load case study it does something like a ForEach with an IfLetStore instead but I thought that might be particular to that example?

Given the above (if it's in fact correct):

1. When the user taps the Delete button in the detail view I send a .deleteTapped action in to my child store. It gets consumed by the parent store (the one that holds the list) and the corresponding item is deleted. Is there a TCA way to get the child view to pop back to the parent view? I'm not even sure how to programmatically "pop" a view using NavigationView at all.
2. I use TCA's ConfirmationDialog feature, and so when the user taps Delete I show a dialog that then sends the .deleteConfirmed action (this is the one the parent actually consumes) but then it also sends a .dialogDismissed action to the child store to dismiss the dialog. This second action causes some warnings in the console because the first action (delete) causes the child state to be deleted in the parent and so it thinks I'm sending an action to a child that no longer exists.

Sorry if this is all a bit ignorant. I did enjoy the UI building part of SwiftUI so far, but handling the data flows and integrating it with TCA has been a bit trickier.

Thanks

[tylerjames]

For some reason I think that when I delete the model used in the Detail view from the parent collection that the Detail view should automatically be popped off. When I run this feature in an independent preview app that's what happens. But when I embed the feature in to my (mostly UIKit) app using UIHostingController pushed onto a UINavigationController stack it doesn't pop off automatically.

Maybe I've got some of the wiring wrong.

[tylerjames]

I fixed both issues as described here:
#1817 (comment)

I had to set the confirmationDialog state to nil before sending the deleteConfirmed action in the parent reducer. And then I did a manual dismiss of the detail view before sending the deleteConfirmed so that the parent would receive no more actions from the now deleted child.

Not sure if this is the correct way to handle this stuff but it works satisfactorily.