-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Dev: Remove the image
ignore errors in phpstan-baseline.php
#7765
Conversation
@@ -723,7 +727,7 @@ public function __call(string $name, array $args = []) | |||
* This function lets us re-proportion the width/height | |||
* if users choose to maintain the aspect ratio when resizing. | |||
*/ | |||
protected function reproportion() | |||
protected function reproportion(): void |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry, can you make this as PHPDoc instead? I mistakenly written yesterday in your earlier PR that it is protected so we can add the : void
directly. I meant it is final
. With your change it will violate LSP for those people extending the methods.
Please revise the same with the other protected methods.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should the image exception return type also be written in the comments?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm in favor of leaving the exception return types in place. Framework exceptions are explicitly for framework code - so even though they aren't marked @internal
they still should not be extended - and certainly not their names constructors.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@MGatner then I think we should instead use new self
over new static
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Framework exceptions are explicitly for framework code - so even though they aren't marked @internal they still should not be extended
It is not documented, and I did not know that.
In fact, we could extend these exceptions.
So I oppose this breaking change. It is better to add @internal
or final
in 4.4
branch, and add return type.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think patch versions should not change the signatures of extensible methods.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @ping-yee for this ongoing effort!
Description
See #7731
Checklist: