Add blockAndSend() and approveAndSend() methods to Response class #5
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.
Problem
The current Response class requires method chaining to build responses, but the
send()
method is protected. This creates a gap when you need to immediately block or approve a tool and send the response in one operation.Currently, to block a tool and send the response, you must:
Solution
This PR adds two methods that combine decision-making with sending:
blockAndSend(string $reason): never
- Blocks tool execution and sends responseapproveAndSend(string $reason = ''): never
- Approves tool execution and sends responseUse Case
When building middleware hooks that intercept tool calls (e.g., routing WebSearch to a different API), you need to:
Without these methods, developers must create extended hook classes with custom logic.
Implementation
Testing
Added tests in
tests/Hooks/ExtendedResponseTest.php
to verify:Breaking Changes
None. These are new methods that don't affect existing functionality.
Alternative Considered
Making
send()
public was considered but rejected to maintain encapsulation and prevent misuse of the response flow.