Fix Fatal error on Class 'Illuminate\Filesystem' load #2
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
Fix Fatal error on Class 'Illuminate\Filesystem' not found in /vendor/laravel/framework/src/Illuminate/Workbench/Starter.php on line 16
taylorotwell
added a commit
that referenced
this pull request
Jan 11, 2013
Fix Fatal error on Class 'Illuminate\Filesystem' load
Closed
ethaizone
added a commit
to ethaizone/framework
that referenced
this pull request
Jul 1, 2013
Obfuscate to only characters < 128. For protect this method will break UTF-8 string.
ghost
mentioned this pull request
ghost
mentioned this pull request
ghost
mentioned this pull request
Closed
Closed
taylorotwell
pushed a commit
that referenced
this pull request
Nov 26, 2014
Reset indentation and sort words
christoph-kluge
added a commit
to christoph-kluge/framework
that referenced
this pull request
Apr 22, 2023
taylorotwell
pushed a commit
that referenced
this pull request
Dec 21, 2023
…e string, null given (#49467) * + Added test that reproduces bug * + Added fix that resolves bug * Update src/Illuminate/Filesystem/functions.php Co-authored-by: Mior Muhammad Zaki <[email protected]> * Update src/Illuminate/Filesystem/functions.php Co-authored-by: Mior Muhammad Zaki <[email protected]> * ~ Don't explicitly test for null --------- Co-authored-by: Mior Muhammad Zaki <[email protected]>
LukeTowers
added a commit
to LukeTowers/framework
that referenced
this pull request
Jul 23, 2025
Fixes laravel#56152 which was caused by the incorrect parameters being used for a more specific type hint docblock merged in laravel#55687. This currently causes issues with projects that use static analysis and make use of the $builder->blueprintResolver() method to resolve custom blueprints. Example below: ------ ---------------------------------------------------------------------------------------------------------- Line Database/DatabaseServiceProvider.php ------ ---------------------------------------------------------------------------------------------------------- :109 Parameter laravel#1 $connection of class Winter\Storm\Database\Schema\Blueprint constructor expects Illuminate\Database\Connection, string given. 🪪 argument.type :109 Parameter laravel#2 $table of class Winter\Storm\Database\Schema\Blueprint constructor expects string, Closure given. 🪪 argument.type :109 Parameter laravel#3 $callback of class Winter\Storm\Database\Schema\Blueprint constructor expects Closure|null, string given. 🪪 argument.type ------ ----------------------------------------------------------------------------------------------------------
taylorotwell
pushed a commit
that referenced
this pull request
Jul 23, 2025
* Fix incorrect docblock for custom builder resolvers Fixes #56152 which was caused by the incorrect parameters being used for a more specific type hint docblock merged in #55687. This currently causes issues with projects that use static analysis and make use of the $builder->blueprintResolver() method to resolve custom blueprints. Example below: ------ ---------------------------------------------------------------------------------------------------------- Line Database/DatabaseServiceProvider.php ------ ---------------------------------------------------------------------------------------------------------- :109 Parameter #1 $connection of class Winter\Storm\Database\Schema\Blueprint constructor expects Illuminate\Database\Connection, string given. 🪪 argument.type :109 Parameter #2 $table of class Winter\Storm\Database\Schema\Blueprint constructor expects string, Closure given. 🪪 argument.type :109 Parameter #3 $callback of class Winter\Storm\Database\Schema\Blueprint constructor expects Closure|null, string given. 🪪 argument.type ------ ---------------------------------------------------------------------------------------------------------- * Update src/Illuminate/Database/Schema/Builder.php * Apply suggestions from code review
tivvie
added a commit
to mogic-le/php84-laravel-framework-11
that referenced
this pull request
Sep 24, 2025
…f type string is deprecated
tivvie
added a commit
to mogic-le/php84-laravel-framework-11
that referenced
this pull request
Sep 24, 2025
…f type string is deprecated
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.
Fix Fatal error on Class 'Illuminate\Filesystem' not found in /vendor/laravel/framework/src/Illuminate/Workbench/Starter.php on line 16