Navigation Stack issue

[easiwriter]

I've been trying to implement Stack Navigation in my AppFeature using your Stacks video and have hit a scoping issue in the AppView.

Here's the code with the error shown:

And here is the path reducer:

There is something wrong with the action parameter, but I'm blowed if I can work out what.

[mbrandonw]

Hi @easiwriter, you will need to share more code, such as what the AppFeature state and actions look like. You can also refer to the docs for more information on using navigation stacks.

[easiwriter]

I have spent more hours trying to get NavigationStack to compile, in particular:

NavigationStack(path: $store.scope(state: \.path,
                                   action: \.path))

I get the following errors, yet the same code in SyncUps compiles. This makes no sense.

I'm sure this is one of those situations where the solution is obvious, so please help.

[easiwriter]

I've just got the view to compile by removing some stuff as shown below:

I don't know why but will experiment. I'm away for a week from tomorrow so will attack it again when I get back. Meanwhile any words of advice would be most welcome.

[kevinanderson7]

Hey @easiwriter, I'm not able to download your project to take a look at the moment, but based on the code you have posted above, it looks like you're scoping on the folderList when really all you should need to do is grab the associated value from the folderList case of the switch and pass it to the FolderListView directly. That store from the associated value is already scoped. Here is the code from SyncUps for reference:

} destination: { store in
      switch store.case {
      case let .detail(store):
        SyncUpDetailView(store: store)
      case let .meeting(meeting, syncUp):
        MeetingView(meeting: meeting, syncUp: syncUp)
      case let .record(store):
        RecordMeetingView(store: store)
      }

There may be other errors as well though. I'd need to see the code for RootFeature to have a better idea though.

[easiwriter]

Thanks Kevin. I've just resolved the problem. It was due to faulty nesting of braces and a missing case let. Stupid really, but that's the way it goes.