Add @throws annotation

[VincentLanglet]

What:

• Bug Fix
• New Feature (?)

Description:

HI @gehrisandro @nunomaduro, I recently used this library and got an API exception in production. Currently there is no @throws phpdoc above method to help the developer to be aware exception are thrown and which can be caught.
@throws annotation allow tools like PHPStorm or PHPStan to report not caught exception. I tried to improve the documentation then.

• Since there are multiple exception in this library I introduced a OpenAIThrowable interface which allow to catch all of them.
• Then, I added @throws OpenAIThrowable to every method throwing an exception
• To be sure the documentation is up to date, I updated the phpstan config to check @throws tag: https://phpstan.org/blog/bring-your-exceptions-under-control
• Since $response->getBody()->getContents(); throw a RuntimeException, I introduced a UnreadableResponse exception to encapsulate the default exception (and implements OpenAIThrowable).

Thanks.

Related:

[pkly]

I just added this library to our project and noticed exception throws were missing on higher level interfaces but were added on request interfaces which were used.

This would be a nice addition, but I would instead like to request specific exceptions that are thrown by default implementations to be specified on the interfaces instead of the interface.
Though obviously the interface to be shared across the exceptions is a nice idea.

[VincentLanglet]

but I would instead like to request specific exceptions that are thrown by default implementations to be specified on the interfaces instead of the interface.

The interface should be about contract and not about "default implementations".
This allow different implementations.

Rather than saying exactly the exception thrown in the default implementation (which is difficult because it can change often) it's generally better to throw an Interface, saying "All theses exceptions could be thrown or not" and if someone else implements the interface he can decide which exceptions from the interface he throws.

[VincentLanglet]

@gehrisandro @nunomaduro I rebased the PR if you have time to take a look :)

Thanks a lot.

[pkly]

In that case all of the exceptions should be behind interfaces, though that is rather... annoying.

[VincentLanglet]

In that case all of the exceptions should be behind interfaces, though that is rather... annoying.

You can catch Interfaces, that the same.
You can also write

catch (ExceptionA) {
  // dothings
} catch (ExceptionInterface) {
  // dothings
}

And that way more useful, than a PHPdoc ExceptionA|ExceptionB|ExceptionC|....

Most of the biggest PHP works with interfaces.

[pkly]

My point being biggest frameworks use separate interfaces for specific error types, not a generic one.

[VincentLanglet]

Friendly ping @gehrisandro @nunomaduro do you have time to review ? thanks ! :)