-
Notifications
You must be signed in to change notification settings - Fork 27
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
feat: allow symfony6, update tests for installable set #73
Conversation
…ble set, php for symfony 5 needs to be >=7.2.5
This should be merged upfront #74 |
Is there any progress? Would very appreciate for be able to upgrade to SF6... and now it's the only lib which is still not supported :( |
Sorry for the long wait on this! I am going to take a look at this in the next day or two. |
Hello @danielmorell any news ? |
Dropping support for PHP 7.1 would be a breaking change and would require releasing a new major version. If we are going to release a major version it would probably make sense to make it PHP 8 only, and drop support for all of PHP 7. This is probably all the more true since Symphony 6 requires PHP 8. It would also allow us to take advantage of the new features of PHP 8. Some community feedback on this would be helpful. What does everyone think about releasing a v5? |
@danielmorell In my point of view, this is not a BC Break because composer is handling this. Symfony itself is moveing from 8.0 to 8.1 in Symfony 6.1. I like the Idea to go to PHP 8 and made some modernizations. |
I have created two new branches. We will also want to setup some CI tests to validate changes. I know #74 is adding that. I need to take a closer look at it. Thank you @art-cg for your many contributions! It will take me a bit to look through this PR and grok all the updates. @art-cg if there is anything you think is not obvious, please drop a comment explaining it. |
@danielmorell Thanks for having a look. I changed the base of the PR to the new Branch. Changing the type in composer.json is not obvious. I removed some tests, that are not needed anymore with strong type hints. But this needs testing. I guess I need to find a plugin/tool to check if P.S. This Thursday is my last day at the actual company. So maybe i will send the other PR from another account. |
@@ -51,19 +29,11 @@ public function getExceptionPayload($exception): array | |||
'body' => [], | |||
'framework' => Kernel::VERSION, | |||
'server' => $this->getServerInfo(), | |||
'language_version' => phpversion(), | |||
'language_version' => PHP_VERSION, |
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 we don't send language versions via the API. I might be wrong but I am pretty sure this does not do anything. We might be able to completely remove it.
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.
Author here. I can remove this if you wish. Any other comments on this PR to move things forward?
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 Chris, I am going to merge this with the base 5.x branch. If you would like you can submit a PR to that branch removing it.
Description of the change
Goal: Allow symfony 6
The rest of the changes are to run the tests (installable set)
This PR is based on https://github.com/rollbar/rollbar-php-symfony-bundle/pull/72/files thanks to @janicekt
I think we should allow symfony 6 first, and after that bump the php version. (should be discussed to which one in another issue). With this we can allow "rollbar/rollbar": "^2|^3" if possible.
Type of change
Related issues
Checklists
Development
Code review