Fix incorrect PHPDoc signatures in Response facade #228
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.
Description
This PR fixes incorrect PHPDoc method signatures in the Response facade that don't match the actual implementation in the Response class.
Issues Fixed:
Root Cause:
The facade PHPDoc was incomplete and didn't reflect the actual method signatures in Apiato\Http\Response, causing PHPStan and other static analysis tools to report incorrect parameter counts.
Impact:
• Fixes static analysis errors when using Response facade methods with parameters
• Improves IDE autocompletion and type checking
• Ensures facade documentation matches implementation
Testing:
• No functional changes - only documentation updates
• Existing tests should continue to pass
• Static analysis tools will now correctly validate method calls
Type of change
[✓] Bug fix (non-breaking change which fixes an issue)
[ ] Refactor (refactoring a current feature, method, etc...)
[ ] Code Coverage (adding/removing/updating/refactoring tests)
[ ] New feature (non-breaking change which adds functionality)
[ ] Remove feature (non-breaking change which removes functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
This is a bug fix because the facade documentation was incorrect, causing static analysis tools to report false errors when developers correctly used the Response methods with their proper parameters.