Remove AssistCommand from registered commands
#3
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
The command does not exist
ghost
mentioned this pull request
systempath
added a commit
to systempath/boost
that referenced
this pull request
Sep 28, 2025
The ListRoutes tool was throwing a type error when boolean parameters (except_vendor, only_vendor) were passed because str_replace() was being called on boolean values. This fix adds type checking to handle boolean parameters separately from string parameters. The error was: "str_replace(): Argument laravel#3 ($subject) must be of type array|string, true given" Boolean parameters are now properly passed to the artisan command without string manipulation, while string parameters continue to have wildcard characters sanitized.
systempath
added a commit
to systempath/boost
that referenced
this pull request
Sep 28, 2025
The ListRoutes tool was throwing a type error when boolean parameters (except_vendor, only_vendor) were passed because str_replace() was being called on boolean values. This fix adds type checking to handle boolean parameters separately from string parameters. The error was: "str_replace(): Argument laravel#3 ($subject) must be of type array|string, true given" Boolean parameters are now properly passed to the artisan command without string manipulation, while string parameters continue to have wildcard characters sanitized.
taylorotwell
pushed a commit
that referenced
this pull request
Oct 14, 2025
* Fix boolean parameter handling in ListRoutes MCP tool The ListRoutes tool was throwing a type error when boolean parameters (except_vendor, only_vendor) were passed because str_replace() was being called on boolean values. This fix adds type checking to handle boolean parameters separately from string parameters. The error was: "str_replace(): Argument #3 ($subject) must be of type array|string, true given" Boolean parameters are now properly passed to the artisan command without string manipulation, while string parameters continue to have wildcard characters sanitized. * Fix boolean parameter handling in ListRoutes MCP tool The ListRoutes tool was throwing a type error when boolean parameters (except_vendor, only_vendor) were passed because str_replace() was being called on boolean values. This fix adds type checking to handle boolean parameters separately from string parameters. The error was: "str_replace(): Argument #3 ($subject) must be of type array|string, true given" Boolean parameters are now properly passed to the artisan command without string manipulation, while string parameters continue to have wildcard characters sanitized. --------- Co-authored-by: systempath <12485137+weburway@users.noreply.github.com> Co-authored-by: Pushpak Chhajed <pushpak@laravel.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
The command does not exist