Scope mapping parameters #1516
Unanswered
JacksonUtsch
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Currently
Scope
conforming toReducerProtocol
utilizesWritableKeyPath
orCasePath
as parameters for mapping. I've found a closure to be more flexible with mapping state/action from multiple parent properties or usage with optionals, nested state, etc.. There probably is a performance bump with the path usage but I'm not sure they can cover all these edge cases.Is an alternative initializer warranted for these situations?
Beta Was this translation helpful? Give feedback.
All reactions