This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
NavigationStack(path:root:destination:) not rendering root view when scoping the store into a new one. #2957
Closed
3 tasks done
Labels
bug
Something isn't working due to a bug in the library.
Comments
|
Hi @danielsan22, the problem is in the You aren't composing the var body: some ReducerOf<Self> {
+ Scope(state: \.cardsSets, action: \.cardsSets) {
+ MainFeature()
+ }
Reduce { _, action in
switch action {
case .path:
return .none
case .cardSets:
return .none
}
}
.forEach(\.path, action: \.path) {
Path()
}
} |
|
Since this isn't an issue with the library I am going to convert it to a discussion. Please feel free to continue to discuss over there. |
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
Description
Hi all, first of all, great work on this library!
I wanted to implement navigation within the app I'm working on to learn/practice more about TCA, I implemented a new feature
RootFeaturethat will hold the state of the stack, and added there the initial state of my top most feature to then scope it out and have it as the root of theNavigationStack(path:root:destination)view.But when building the main feature using the RootFeature I only get a white screen, that does loads and sends the initial
.onTaskaction but never updates anything else, even when printing the changes on the reducer I can see that there is no change on the state and no other action is sent even tho the.onTasksends an array of data.However, if I create a new store and pass it to the MainView inside the root parameter of the NavigationStack I do get the screen displaying and all the functionality that I expect, but I haven't found a way of comunicating to the parent
RootFeatureand get the actions that then will trigger the navigation I have defined on theRootFeature.I am unsure if this is something that I should be doing or not or instead focus on having all the navigation logic directly inside the feature that will be the "true" root feature, but I like having my features a bit more isolated, thats why having the RootFeature take care of all the details of the other screens/features makes sense to me, it is also how I understood the docs since the examples use a simple NavigationLink as root (which to my app does not make sense to do that).
Checklist
mainbranch of this package.Expected behavior
The NavigationStack's
rootview can be created using a scoped version of theRootFeature's store and renders and works with all the defined actions.Actual behavior
The NavigationStack's
rootview is not displayed and the console prints out no changes to the sate even when they are hard-coded as when the view loads.Steps to reproduce
I have created a brand new project and recreated the issue there.
The Composable Architecture version information
1.9.2
Destination operating system
iOS 17
Xcode version information
15.0
Swift Compiler version information
The text was updated successfully, but these errors were encountered: