-
Notifications
You must be signed in to change notification settings - Fork 56
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
Extend the Agent and Identities with a metadata field (local storage) #696
Comments
There is already a |
This is what we discussed the other day @csuwildcat |
I have made UI that allow users to rename their accounts, but I don't know how to update and save these changes. Is that even possible? This is from the If I manage the creation of the AgentIdentityApi and the DwnIdentityStore, I can access the Here I attempt to set the updated metadata: Unfortunately it will trigger an error when attempting to set, I don't think I should allow duplicates?
Attempted to first |
@sondreb I recently enabled the ability to update existing records in the IdentityStore using the web5-js/packages/agent/src/store-data.ts Line 141 in 3e68aae
I'm hesitant in allowing a flat out I was leaning towards doing something similar to what I did for DWN Endpoints in my last PR, adding Additionally, these things are quite literally DWN records written to the agent's own DWN, if any additional data is needed by a specific wallet they could in practice install that to the agent as their own protocol and write to it. However if we think there are specific additional fields that we would like to tie to |
It would be nice if we could store a small piece of metadata (JSON) connected to either agent or identities. This way it could be used for friendly names or tags, etc. Would allow me to have some extra information persisted connected to the agents and identities and rely on the storage implementation that the Web5 API gets injected.
The text was updated successfully, but these errors were encountered: