-
Notifications
You must be signed in to change notification settings - Fork 37
clarify batch management in the Wallet when the new batch of the credentials was received #452
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
Conversation
Co-authored-by: Christian Bormann <8774236+c2bo@users.noreply.github.com>
Co-authored-by: Torsten Lodderstedt <torsten@lodderstedt.net>
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.
Related to #472 I think we need to merge the language there as how do you know whether the batch you have just received is materially different to the last one, if you are just obtaining new copies of a credential and the claim values are the same why should you be forced to delete the copies you have at the moment?
tplooker
left a comment
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.
Changing my review based on above comment, easy to resolve I just think we need to check these PR's are consistent with one and other.
|
WG discussion:
|
resolves #124