-
Notifications
You must be signed in to change notification settings - Fork 38
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
[rest] Error handling and validation #125
Labels
Comments
My request body for this error (in Rust debug prints was this): [trace] Some(
Object({
"attachments": String(
"string",
),
"comment": String(
"string",
),
"connectionId": String(
"foo",
),
"credentialDefinitionId": String(
"bar",
),
"preview": Object({
"attributes": Array([
String(
"string",
),
]),
"type": String(
"https://didcomm.org/issue-credential/1.0/credential-preview",
),
}),
}),
) |
Will this be fixed by #148? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Ive had some issues with the errors that are being returned from the api. For example, I think I forgot a field in the
credentials/offer-credential
endpoint and this was the response:I believe if we only send the
message
field,Cannot read properties of undefined (reading 'startsWith')
back it will already be a lot better. But this error also goes into my second point, startsWith is being called on undefined, so apparently I forgot a value in my call but I have no idea which one.Some stricter validation with better error messages would be insanely benificial.
The text was updated successfully, but these errors were encountered: