You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{
"id": "d513f09a-11df-4fb7-a258-71acafc780f0",
"errors": [{
"code": 403,
"reason": "A request failed due to a missing or invalid csrf_token value.",
"status": "Forbidden",
"message": "The requested action was forbidden"
}]
}
As you can see, the error key is an array not an object.
I looked into this a bit, the problem right now is that the error could also have a different layout, which is why this is currently polymorph. One problem are for example system errors that do not have a proper JSON object representation. So this needs to be fixed in both the server as well as the swagger spec, but it's a bit more work :)
Describe the bug
The current typescript type for
ErrorContainer
inapi.d.ts
doesn't correctly represent the payload.Reproducing the bug
Look at the typescript bindings to see the
ErrorContainer
type.Generate an error and look at the payload.
As you can see, the
error
key is an array not an object.The correct type would be:
Environment
Both server and client package are
0.5.0-alpha.1
The text was updated successfully, but these errors were encountered: