[TASK] Use native type declarations in OutputFormatter
#964
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
oliverklee
added this to the
9.0.0: Drop support for PHP < 7.2 and clean up things milestone
Also improve a related type annotation. Part of #811.
oliverklee
force-pushed
the
task/types/outputformatter
branch
from
27fb2b0 to
cc51921
Compare
JakeQZ
approved these changes
Feb 20, 2025
| */ | ||
| public function safely($cCode) | ||
| public function safely(callable $cCode): ?string |
There was a problem hiding this comment.
👍 callable appears to be the correct parameter type, rather than string.
Comment on lines
+29
to
+30
| (#641, #772, #774, #778, #804, #841, #873, #875, #891, #922, #923, #933, #958, | ||
| #964) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Also improve a related type annotation.
Part of #811.