Skip to content

[11.x] Fix Application::interBasePath() fails to resolve application when project name is "vendor"#54871

Merged
taylorotwell merged 3 commits into
11.xfrom
11/issue-54869
Mar 3, 2025
Merged

[11.x] Fix Application::interBasePath() fails to resolve application when project name is "vendor"#54871
taylorotwell merged 3 commits into
11.xfrom
11/issue-54869

Conversation

@crynobone
Copy link
Copy Markdown
Member

fixes #54869

project name is "vendor"

fixes #54869

Signed-off-by: Mior Muhammad Zaki <crynobone@gmail.com>
Signed-off-by: Mior Muhammad Zaki <crynobone@gmail.com>
Signed-off-by: Mior Muhammad Zaki <crynobone@gmail.com>
default => dirname(array_values(array_filter(
array_keys(ClassLoader::getRegisteredLoaders()),
fn ($path) => ! str_contains($path, '/vendor/'),
fn ($path) => ! str_starts_with($path, 'phar://'),
Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Checking for phar:// would solve the original bug #54118 and still allows vendor

@crynobone crynobone changed the title Fix Application::interBasePath() fails to resolve application when project name is "vendor" [11.x] Fix Application::interBasePath() fails to resolve application when project name is "vendor" Mar 3, 2025
@taylorotwell taylorotwell merged commit 1154a31 into 11.x Mar 3, 2025
@crynobone crynobone deleted the 11/issue-54869 branch March 4, 2025 00:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants