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
API Problem response with HTTP status code from exception when it's valid rage of HTTP codes. But what about situation when some library throws own exceptions, with own codes (example 302, and it means that user doesn't exist)? It does't make sense.
My solution for this is to use code from exceptions only when exception implements \ZF\ApiProblem\Exception\ExceptionInterface
Problem details are not a debugging tool for the underlying implementation; rather, they are a way to expose greater detail about the HTTP interface itself.
API Problem response with HTTP status code from exception when it's valid rage of HTTP codes. But what about situation when some library throws own exceptions, with own codes (example 302, and it means that user doesn't exist)? It does't make sense.
My solution for this is to use code from exceptions only when exception implements
\ZF\ApiProblem\Exception\ExceptionInterface
Originally posted by @snapshotpl at zfcampus/zf-api-problem#26
The text was updated successfully, but these errors were encountered: