-
Having a general "ApiProblem" exception is a bit unconvenient. We should have speicifc exceptions classes for most used errors, like what I was doing in ZfrRest: https://github.com/zf-fr/zfr-rest/tree…
-
I ran into an issue when injecting a service which needed a Sql object (also injected) but there were missing credentials which caused the database to throw an exception. The code from the db was 7 wh…
-
Hi @weierophinney ,
I run into an interesting use case and I couldn't solve it.
The problem is that ApiProblem is no longer an exception class, so I cannot throw any ApiProblem. It seems the only wa…
-
As I was working with Apigility, I noticed that filters did not get applied.
I went through the code with a collegue, and found that it does get applied on DB-connected resources.
See; https://gith…
-
Use of JSON_UNESCAPED_SLASHES in
https://github.com/zfcampus/zf-api-problem/blob/master/src/ZF/ApiProblem/ApiProblemResponse.php#L45
Is only available as of PHP 5.4.0.
Composer says that only PHP…
-
My own notes of things to not forget about or revisit as I create the project for this tutorial:
- [x] Look into plural of URL patterns - `/programmers/...` versus `/programmer` - I can't remember whi…
-
I have an POST operation to a resource and have validators on multiple entity properties.
I know that I can throw an CreationException() with a message, with for example the first validation error. B…
-
Hello,
im throwing a custom exception while processing the update-event of the resource-listener. Unfortunately the exception code will be used as http response code.
```
public function onUpdate(E…
-
The spec allows additional fields for API-Problem, these could be provided via an array in the constructor, something like this extension:
``` php
-
`ApiProblem` has a list of problem status titles that could easily be expanded to cover all valid status codes. This would leave the `$problemStatusTitles` property no longer providing status titles …