Class 'ipinfo\ipinfo\Exception' not found about php HOT 12 CLOSED

@coderholic @scofield-ua I'll take a look later today and will fix/close this issue.

from php.

@jhtimmins
A function definition must include all uncatched exceptions. The exceptions may rise inside the function code or inside other functions that your original function calls. The functions that you call use Guzzle, and Guzzle functions throw \GuzzleHttp\Exception\GuzzleException. You don't catch exceptions from Guzzle therefore you pass them to the user. As a result you have to specify the \GuzzleHttp\Exception\GuzzleException in the PHPDoc.

from php.

This was fixed in commit 6068f65.

I've added an IPinfoException class which will get returned instead of the base Exception class or the GuzzleException class.

from php.

Add in PHPDoc that the function may rise an Exception

from php.

@coderholic

from php.

@jhtimmins

from php.

@scofield-ua my apologies, I ran into some issues with my computer so I'm having trouble testing this, which may delay me a bit.

In the meantime, could you clarify why it's necessary to import Exceptions from multiple locations?

from php.

@jhtimmins no problem, thanks.

I think the main idea of this issue is to fix the part where you're throwing global Exception class. For example here:

Right now global Exception class is throwing in local namespace: ipinfo\ipinfo, which is causing fatal error.
Need to use throw new \Exception instead of throw new Exception, or just connect it at the beginning of the class.

In my project I'm currently have to catch Throwable exception.

Also, I think, instead of general global Exception class would be good to throw some custom named exception which is related only for IpInfo package, something like IpInfoException which you can use to throw any kind (or specific kind) of errors.

from php.

@jhtimmins, the comment of @scofield-ua is absolutely correct. That's what have been done in my PR #5
Additionally I added the correct information about the exceptions in PHPDoc.

from php.

@scofield-ua Ah of course, yes that makes sense. I actually thought you submitted the PR with multiple exception types, which should have been directed at the PR author. Thanks for the info.

@rvalitov Could you explain this docblock, and why it includes two exception types?

     * @throws \GuzzleHttp\Exception\GuzzleException
     * @throws \Exception

It doesn't look like \GuzzleHttp\Exception\GuzzleException will ever get thrown directly. Or am I missing something?

from php.

😊

from php.

If 6068f65 does not resolve this issue, please let me know and we can reopen.

from php.