Repository navigation
Map properties to contact fields with ##contact - #507
Open
andrewaylett wants to merge 1 commit into
Open
andrewaylett wants to merge 1 commit into
andrewaylett wants to merge 1 commit into
Conversation
A phone's contacts have fields (phone numbers, emails, addresses and so on), and Quiddity's properties are free text, so something has to say which property fills which field. Following the other meta-properties, a property's entity says it: `##contact(phone:mobile)` on `mobile` makes its values mobile phone numbers. The field is one of a fixed few, and the label after the colon is free. Nothing uses the mapping yet. This reads it into the schema, lists the mapped properties on the index, and flags a line it can't read; the contacts themselves come in the commits stacked on this one. Journal: - Added `##contact(field:label)`, which says which field of a contact a property fills. [[Contacts]] [[Built-in properties]] - It is the first step towards showing entities in Android's contacts: only the mapping is read so far, and [[Contacts]] says so. - Any entity with a value for a mapped property will be a contact, with no type to say it is a person, so the mapping is all a graph has to write. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01URxBNGtnCj5RibKerde9WL
andrewaylett
force-pushed
the
claude/hopeful-gates-6pytdj
branch
from
November 22, 2026 01:01
7771958 to
6a4b1de
Compare
|
This branch has not been deployed
This file contains hidden or 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
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.



First of a stack that shows entities in Android's contacts.
A property's entity says which field of a contact its values fill:
##contact(phone:mobile)onmobile. The field is one of a fixed few (phone,email,address,organisation,job-title,nickname,website,birthday,note) and the label after the colon is free. An entity with a value for a mapped property will be a contact; there is no type to say it is a person.This only reads the mapping into the schema, lists the mapped properties on the index (
Index::contact_keys) and flags a line it can't read. Nothing uses it yet; the new Contacts docs page says so.The stack: this, then #508 (the contacts crate) and #509 (reconcile), with the Android side to follow.
🤖 Generated with Claude Code
https://claude.ai/code/session_01URxBNGtnCj5RibKerde9WL