Open snapshotpl opened 9 years ago
:+1:
Via http://tools.ietf.org/html/draft-nottingham-http-problem-07#section-4
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.
This repository has been closed and moved to laminas-api-tools/api-tools-api-problem; a new issue has been opened at https://github.com/laminas-api-tools/api-tools-api-problem/issues/7.
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