refactor: Add backwards-compatible return types ahead of symfony8 #1702
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Extracted from work by @Kocal in Behat#1687 - these return types will be required in 4.x for symfony8 support, but can be added in 3.x without any BC impact as they are either final classes or internal test code. This will reduce potential for future conflicts merging 3.x up to 4.x.
stof
approved these changes
Nov 24, 2025
carlos-granados
approved these changes
Nov 24, 2025
Contributor
carlos-granados
left a comment
There was a problem hiding this comment.
Thanks @acoulton
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Extracted from work by @Kocal in #1687 - these return types will be required in 4.x for symfony8 support, but can be added in 3.x without any BC impact as they are either final classes or internal test code.
Adding them now will reduce potential for future conflicts merging 3.x up to 4.x.