-
Notifications
You must be signed in to change notification settings - Fork 18
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
Improve language/examples around test suite API. #134
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.
We might want to change the requirements from verifying an eddsa-rdfc-2022 to processing, this will ensure jose folks can just process the payload without having to verify the proof (which isn't tested here anyways)
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.
@aljones15 would love your thought here on API variations.
Co-authored-by: Patrick St-Louis <43082425+PatStLouis@users.noreply.github.com> Co-authored-by: Ted Thibodeau Jr <tthibodeau@openlinksw.com>
Co-authored-by: Ted Thibodeau Jr <tthibodeau@openlinksw.com>
126d138
to
842e87a
Compare
@PatStLouis GitHub seems to think I didn't satisfy your requested change. Could you re-review this one? Thanks! |
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.
Might as well align with the problemDetails
as defined in the specifications
We can do that in the README, but does any of the code handle that yet? |
To match upstream VC API approach. Per code review feedback from @PatStLouis. Co-authored-by: Patrick St-Louis <43082425+PatStLouis@users.noreply.github.com>
No description provided.