-
Notifications
You must be signed in to change notification settings - Fork 11.3k
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
[5.1] Fix Model forceDelete return type doc #9624
Conversation
Applied same return type and throws doc as the `delete()` method.
I'm pretty sure |
If that's the case, then the A value is being returned from the |
No? I'm not sure you understand? We're saying you CAN rely on the return type of delete, but not of forceDelete. |
That means we can change forceDelete to whatever we want it to return in the future and it's not a breaking change. |
If this is the case, then why would you have a return type on the I'm failing to see what sort of other information would be returned to a developer if the implementation ever needed to change? And if this did change, wouldn't it be listed as a breaking change and have the return type modified just like all other methods? |
We're not saying it doesn't return a Why is that so hard to understand? |
Through the return type listed as But, ok 👍 |
NO! I'm not saying it returns nothing. I'm saying it returns ANYTHING. |
Ie, UNDEFINED. |
Then the return type should be |
I guess the reason for this choice is that the real |
|
|
Not in PHP though... http://php.net/manual/en/language.pseudo-types.php
|
Ok 👍 |
Applied same return type and throws doc as the
delete()
method.