feat: allow symfony6, update tests for installable set

[art-cg]

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

• [ ] Bug fix (non-breaking change that fixes an issue)
• [x] New feature (non-breaking change that adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
• [x] Maintenance
• [ ] New release

Related issues

Shortcut stories and GitHub issues (delete irrelevant)

• Fix [SC-]
• Fix #1

Checklists

Development

• [ ] Lint rules pass locally
• [ ] The code changed/added as part of this pull request has been covered with tests
• [x] All tests related to the changed code pass in development

Code review

• [x] This pull request has a descriptive title and information useful to a reviewer. There may be a screenshot or screencast attached
• [x] "Ready for review" label attached to the PR and reviewers assigned
• [ ] Issue from task tracker has a link to this pull request
• [ ] Changes have been reviewed by at least one other engineer

[art-cg]

This should be merged upfront https://github.com/rollbar/rollbar-php-symfony-bundle/pull/74

[scorpioniz]

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 :(

[danielmorell]

Sorry for the long wait on this! I am going to take a look at this in the next day or two.

[YaHkO]

Hello @danielmorell any news ?

[danielmorell]

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?

[art-cg]

@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 upgraded the Code to PHP8 and make a lot of changes in the last commit. It would be great to have some tests from real Applications.

[danielmorell]

I have created two new branches. next/4.x/main will hold the source for v4 and any minor/patch updates to that version. next/5.x/main. will hold all contributions to the future v5 release. Once it is ready for the official 5.0.0 release we will merge it into the master branch. We will try to make sure there are some beta releases so that people can test before the official 5.0.0 release.

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.

[art-cg]

@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. https://symfony.com/doc/current/bundles/best_practices.html#installation

I removed some tests, that are not needed anymore with strong type hints. But this needs testing. phpunit.xml was migrated with the integrated migration command. @package Notation and "useless" comments/docblocks are removed. The ArrayShape Notation is specific to the IDE PhpStrom and helps to understand the code. Of course it is finde to revert that change. pleas let me know.

[ArrayShape(['exception' => "array", 'frames' => "array"])]

I guess Tests/Fixtures/fatal.php can be removed. I am not sure why it is there. WDYT? i would delete /var/.gitkeep as this folder is created on the fly by running tests. WDYT? Readme.md could be improved and remove old projects. But that should be another PR.

I need to find a plugin/tool to check if Resources/doc/index.rst file could be parsed correct.

P.S. This Thursday is my last day at the actual company. So maybe i will send the other PR from another account.