Support KeyPaths with multiple return types #1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hello.
I’m planning to use this in my project, but I’m stumbling on some things.
When using multiple
KeyPath
s, you cannot specifyKeyPath
s with different return types at the same time, because generic types of theKeyPath
array is inferred and limited to one type.So to make it more flexible, I changed the argument of the function to a set of
PartialKeyPath<Value>
(type-ereasing).The return type isn’t that important since it’s only for detecting value changes.
Also there was an issue where the event wouldn’t fire when the SwiftUI view was updated and the
wrappedValue
changed, so I made it to rehook when the setter was called.