Pablo Largo Mohedano

Maybe a good implementation on the omnipay-common side would be an `\Omnipay\Common\Http\Exception\TooManyRequestsHttpException` extending `\Omnipay\Common\Http\Exception\InvalidRequestException` in the line of the `symfony/http-kernel` component. WDYT @judgej?

I've had this problem, take a look at https://github.com/symfony/symfony-docs/issues/17636#issuecomment-1665172764

> @devnix one thing I realized here: you may get resource objects, in case of LOBs? 🤔 (╯°□°)╯︵ ┻━┻

I've added another `non-empty-` and I think that should be all. Now I can take a look at each implementation. In the cases where the types are not guaranteed but...

I think these changes are correct, if there is any other API I can improve in this PR let me know! I observed some `Result` classes that with another internal...

Not sure what's up with those `Invalid inline documentation comment format "@var (non-empty-list | false)", expected "@var type $variableName Optional description".` 🤔

Little ping here @derrabus, I think all the requested changes are done, if you want to approve the workflows 😃

I can rebase and solve conflicts, but I don't know if there is interest in merging this pull request, feedback would be welcome 🙂

Yup, I'll want to finish a couple of contributions to PHPStan and Psalm first related to this pull request 😄

I'll be sure to leave here an idea. As we probably want to have fine control of what is `some` and what is `none` and each view will likely differ,...