-
Notifications
You must be signed in to change notification settings - Fork 56
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Return types of API responses are void #4
Comments
This really needs updating. |
This issue is open now for about three months. When can we expect this to be fixed? This is really bad because all code quality tools warn about this. I find it worth considering, that the official client seems to have a lower quality than the community library. |
Hello @alexandersch . Thanks for your report. I can confirm that this is a problem and we will fix it in the future versions of the library. It is in our backlog. |
1 year to update doc block seems to be too much ;) |
+1 When this fix will be resolved? :) |
Closing this issue since we fixed on #59 |
A lot of times the return type of API calls are void when they are returning an array of data. Could you please update them to a correct value?
E.g.:
@return void response from the API call
To:
@return mixed response from the API call
Or:
@return array response from the API call
Thanks in advance.
The text was updated successfully, but these errors were encountered: