-
-
Notifications
You must be signed in to change notification settings - Fork 300
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
version 4.5.3 #1447
version 4.5.3 #1447
Conversation
I would prefer if #1432 is fully resolved before 4.5.3 is released. |
Co-authored-by: Benoît Viguier <ildyria@users.noreply.github.com> Co-authored-by: github-actions[bot] <action@github.com>
This reverts commit 92b6bb8.
Me, too. Updating php-exif is only half of the solution, we also need to fix I am a little bit surprised that we suddenly push out on release after the next. |
I was just matching the tags. Don't overthink it :) |
Why are there so many changes in whitespace? This is annoying. |
This was a php-cs-fixer update. |
That is not a good point. Even if Let's say that we wanted to to change the current behaviour and let's say we decide to be PSR-12 compatible (see https://www.php-fig.org/psr/psr-12/#3-declare-statements-namespace-and-import-statements), then I would understand that. But the current change is not even achieve PSR-12 compatibility, but looks rather random as if nobody took care. |
I fixed some of the sporadic changes made by CS Fixer in bab6011. I haven't yet found out what newly introduced option controls the removal of parentheses. Don't get me wrong. I am not against formatting changes. For example, I could envision to move to PSR-12 coding standard. But this decision should be made explicit and it should be in an independent PR. It should not happen accidentally and it should not be mixed with a PR which also introduces functional changes. |
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.
Formally, I am entitled to do a review (as @ildyria is the submitter), but I would prefer if someone else could to a review, because most of the actual changes are on me.
I can do the review though. :) |
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.
LGTM. ( I can't click approve though :( )
I guess you should be good to go? 😄 |
version 4.5.3 + composer update to add php-exif v0.7.11