-
Notifications
You must be signed in to change notification settings - Fork 464
PHP 8.1 + Symfony 6.0 #675
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
Conversation
384fe3d
to
0c65ea5
Compare
@mihaileu It's ready :) I had to drop the older PHP versions to be able to upgrade to the latest PHPUnit version. Since they are not supported anyway, I think this is good. |
@ruudk Please resolve conflicts, and I hope this PR will be merged soon. |
Drop all unsupported PHP and Symfony versions. Bump Ubuntu Drop stability and experimental
@javer done |
@mihaileu Could you please review this PR? |
What's the point exactly? Is there any problem with using this bundle with newer Symfony or PHP version without those changes? So far bundle works with older versions and doesn't force users to upgrade whole projects just because this Bundle updated. Also it is very good practice to squash commits for PR. |
I wouldn't have done this work if it wasn't needed obviously. There is no point in keeping this bundle in par with unsupported PHP versions. People on those versions should upgrade or keep the older releases of this bundle.
That's your opinion. That's not how I work. |
@Eloar Of course it cannot be used with newer Symfony version, because it cannot even be installed at all:
That's how composer constraints work: Lines 13 to 21 in 777bd90
|
Can confirm that proposed changes works great in the real project with Symfony 6.0 and PHP 8.1. |
So there is no point for dropping support, just extending it for new Symfony version. Old Symfony versions support is not a problem, the problem is lack of Symfony6 support. I would recommend not changing lower versions constraints until it became problem for bundle. It is not up to a bundle to enforce people to upgrade projects. |
@Eloar Feel free to create a PR and do it your way. |
@ruudk to conflict changes in active Pull Request? That would be counterproductive. Decision is up to Bundle owner I just shared opinion. I like how liberal this bundle is. |
PHPUnit 9.3+ is required to support PHP 8.0, and PHPUnit 9.5 is actually required to support PHP 8.1. |
@javer is there a point to drop PHPUnit ^7.5|^8.5 version constraint and not just extend it with ^9.5 for PHP 8.1? |
@ruudk @javer thx for this PR |
Regarding PHPUnit compatibility, You can use same workaround as we did here php-amqplib/php-amqplib@393546c#diff-96a82592013e5f4b91e682332583b7a4a6ca1ff0431d267c61179b1a21b167daR6 |
Feel free to use my PR and improve it further. I'm not going to change it and support PHP versions that are EOL. Sorry. It took me already way too much time. |
"symfony/config": "^4.3|^5.0", | ||
"symfony/yaml": "^4.3|^5.0", | ||
"symfony/console": "^4.3|^5.0", | ||
"symfony/dependency-injection": "^4.4|^5.3|^6.0", |
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.
why ^5.3, isn't it working with older versions of 5 ?
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.
https://symfony.com/releases , only 5.3 is supported, the rest is EOL
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.
@ramunasd I see no reason to let old compatibility with php and symfony EOL. We will keep same major tag an increase the minor. There's kinda enough time passed in order to not affect too much people or at lease suggest them an update. What do you think ?
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.
AFAIK symfony 4.4 and 5.4 are LTS releases, we can stick to them
@@ -654,7 +654,7 @@ protected function injectConnection(Definition $definition, $connectionName) | |||
$definition->addArgument(new Reference(sprintf('old_sound_rabbit_mq.connection.%s', $connectionName))); | |||
} | |||
|
|||
public function getAlias() | |||
public function getAlias() : string |
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.
is there a space between ) and : ? if yes, we should eliminate that in order to stick as much as possbile with PSR12
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.
php-cs-fixer should do this.
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.
Let's add PSR12 style check for all PR's. These things should be noticeable automatically.
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'll add php-cs-fixer as github action
Didn't expect this to be merged, thank you! @mihaileu 🎉 |
thanks for your contribution |
Fixes: