Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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 #7765Dev: Remove the
image
ignore errors in phpstan-baseline.php #7765Changes from 2 commits
5435ea3
8e42ddf
773ee48
eac79d8
7ecc708
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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 isfinal
. 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
overnew 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.
@MGatner @paulbalandan
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
orfinal
in4.4
branch, and add return type.