Using navigation with ReducerProtocol

[jjjeeerrr222]

I am using the ReducerProtocol and in my reducer I have an ifLet to another screen to scope its state. I want to also use the sheet navigation with a Destination to match its case. Do I need to have both a feature.state property and a feature.state case to do this?

State:

public struct State: Equatable {
        var gameFeature: GameFeature.State? = nil
        var destination: Destination? = nil
        
        public enum Destination: Equatable {
            case game(GameFeature.State)
        }
        
        public init(destination: Destination? = nil) {
            self.destination = destination
        }
    }

Reducer:

public var body: some ReducerProtocol<State, Action> {
        Reduce(self.core)
            .ifLet(\.gameFeature, action: /Action.gameFeature) {
                GameFeature()
            }
    }

Is this correct or should I somehow only be using the state defined within the enum for the .ifLet in my reducer

[mbrandonw]

Hi @jjjeeerrr222, unfortunately this library isn't really meant to be used in conjunction with TCA, which requires more involved tools. Those tools will be coming soon though. In the meantime I suggest opening a discussion in TCA if you want to ask others how they handle navigation right now.

[jjjeeerrr222]

@mbrandonw Thanks for the answer. That is currently how I have been using it and it works although I need to manage 2 pieces of state for any given destination which is error prone.

Looking forward to seeing how this will work with TCA