-
Notifications
You must be signed in to change notification settings - Fork 55
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
No id creation #25
No id creation #25
Conversation
Signed-off-by: blu3beri <[email protected]>
Signed-off-by: blu3beri <[email protected]>
Signed-off-by: blu3beri <[email protected]>
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.
Woot, great work @blu3beri!!
@dkulic this is probably also relevant to you, as it touches some things you were also working I think |
Signed-off-by: blu3beri <[email protected]>
Signed-off-by: blu3beri <[email protected]>
Signed-off-by: blu3beri <[email protected]>
Signed-off-by: blu3beri <[email protected]>
@TimoGlastra I have added some wrappers around the anoncred identifiers. If we need validation on an Anoncreds object it can easily be added. |
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, but not a rust developer so maybe someone should take a look at it aswell :)
@andrewwhitehead -- can you take a look, per @TimoGlastra request? |
Just as a note, I will create a follow up PR doing some cleanup for the codebase. |
@whalelephant feel free to also leave a review if you have time |
Wow, great work. Thanks. |
Signed-off-by: blu3beri <[email protected]>
Signed-off-by: blu3beri <[email protected]>
Signed-off-by: blu3beri <[email protected]>
Signed-off-by: blu3beri <[email protected]>
@@ -70,8 +67,8 @@ pub struct CredentialInfo { | |||
pub referent: String, | |||
pub attrs: ShortCredentialValues, | |||
pub schema_id: SchemaId, | |||
pub cred_def_id: CredentialDefinitionId, | |||
pub rev_reg_id: Option<RevocationRegistryId>, | |||
pub cred_def_id: String, |
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.
Is there any reason why we do not use CredentialDefinitionId here?
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.
Ah I think that one was not changed, I will update this.
Signed-off-by: blu3beri <[email protected]>
Signed-off-by: blu3beri <[email protected]>
I used quite a bit of |
Signed-off-by: blu3beri <[email protected]>
Signed-off-by: blu3beri <[email protected]>
Signed-off-by: blu3beri <[email protected]>
Signed-off-by: blu3beri <[email protected]>
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
closes #4
closes #13
closes #23
It also picks up some tasks from other tickets. Mainly with regards to the "remove to_unqualified...".
Might have to do some clean up (most
String
can be converted to&str
).There are two major TODOs which I need some help with.
Right now we have some presentation filter, like: schema issuer, schema name, etc. Before we could derive this from the schema id, but not anymore. How will we deal with this? As the schema id has no guarantee of being "qualified" we can not use it.
I believe we can do these from the filters without changing anything:
We can allow for more data to be passed in which can be gotten from an object resolution on the ledger or whatever.
The second one is the wrappers. I did not update them, but updating them would be trivial as they are just FFI-wrappers without complex logic build atop. I can create an issue for that if there is none.