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
@FloopCZ yes - this is about the specification file (swagger.json). If an endpoint accepts any parameters (be it through the request body, path, query string, header...), there is a chance that the parameters will be invalid. Therefore, it might be reasonable to fill in the 400 response in the specification implicitly.
I'm still not sure about this. With today's Apistrap, it is possible to just add :raises InvalidFieldsError to the docblock and the response will be declared in the spec. Is it worth it to try to fill it in implicitly? @petrbel@blazekadam@FloopCZ
It's probably worth a try to think of all exceptions an endpoint can throw - not only InvalidFieldsError, but also stuff like Unauthorized or ForbiddenRequest.
No description provided.
The text was updated successfully, but these errors were encountered: