Store unique IDs back to the native Contacts store. #69
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ions are calling it.
In point of fact, store the unique ID as a URL address field of type "HelloAgain" in the corresponding native Contact record. This custom URL will actually be visible to the user, and be _clickable_ once we get deep links into the app wired up in iOS. The deep link takes the form: helloagain://to/first-last-abcd The code currently writes back the unique deep link whenever a friend is toggled. Also, when contacts are imported, they're searched for missing deep links and the links are written back at that time, although this shouldn't really happen. What's great about this is that now any aspect of a native contact record can change (aside from the HelloAgain deep link) and the contact's identity will still match up with their HelloAgain friend record -- even across devices (or even possibly platforms, when we get that far).
|
+1 |
…s reducer. It seems weird to put a side-effect in an action *creator* but I don't have better ideas.
schuyler
force-pushed
the
schuyler-store-id
branch
from
a8095a9
to
eeb188e
Compare
|
Closes #66 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
In point of fact, store the unique ID as a URL address field of type "HelloAgain" in the corresponding native Contact record. This custom URL will actually be visible to the user, and be clickable once we get deep links into the app wired up in iOS.
The deep link takes the form:
helloagain://to/first-last-abcdThe code currently writes back the unique deep link whenever a friend is toggled. Also, when contacts are imported, they're searched for missing deep links and the links are written back at that time, although this shouldn't really happen.
What's great about this is that now any aspect of a native contact record can change (aside from the HelloAgain deep link) and the contact's identity will still match up with their HelloAgain friend record -- even across devices (or even possibly platforms, when we get that far).
@obra!