This repository has been archived by the owner on Jan 24, 2023. It is now read-only.
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.
I am suggesting this addition to
Snail
. This allows to map aUnique<T>
into aUnique<U>
that will receive the same notifications, with thevalue
transformed from its initial typeT
to the expected new typeU
.This is useful for me here when I use:
But in my case, I need to bind
viewModel.showingAgent
which is of typeUnique<FullContact?>
. I don't want to create a new enumeration member taking that type specifically. I prefer to reuse that existing enumeration member and mapviewModel.showingAgent
into aUnique<String?>
.I think this could be useful in multiple places as well along the way 馃憤