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.
As discussed in #928 this is the first task needed for modernization (in my point of view).
There is of course a lot of space for improvments. But i do not want to do, to many things at once.
@pierredup @johnkrovitch
Maybe you can branch from
master
a new develop-branch2.x
for modernization.So i can take new branch as base for this PR. Advantage:
master
stays clean for other changes.From that point we can improve that branch by ...
[ ] Add Typehints on internal API (avoid BC breaks)
[ ] Use new Language Features of PHP 8
[ ] Remove external deprecations (PhpUnit, ...)
[ ] Move Travis to github actions (Run tests on each repo separately)
[ ] Update Dependencies: Example: Possible BC Break: php-http/guzzle6-adapter => php-http/guzzle7-adapter
[ ] TODO
And after all that is done, new Interfaces and more complex code changes can be done.
So this single PR ist not getting bigger and bigger.
WDYT?