-
Notifications
You must be signed in to change notification settings - Fork 226
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: marshal based on user's petnames #1092
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! Very nice!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
This is a great start on a petname system. What is here is all valid. Future directions (not in this PR please!):
A more full featured petname system would enable the user to assign and change petnames for existing objects afterwards. Ideally, all renderings of that petname on a UI would be updated then. My android phone contacts lists seems to do this perfectly.
A more full featured petname system would have gentler fallbacks before retreating to unnamed-37
, such as pathnames. However, pathnames depends on more information being available than can be available to this module or communicated through marshal
.
This PR adds a library for hydrating and dehydrating values based on a system of the user's petname maps. The next step is using this library in the wallet.