[Feature]: Setting basepath of laravel project

[cfong63]

Feature Description

Feature Description

Description:

Current behaviour is that Laravel extension only starts working if VSCode is opened at the root of the laravel project
Our current repository has the laravel project as a subdirectory of the bigger git repo.
Such that:

./.git
./laravel/
./etc/

I noticed that opening vscode in the laravel subdirectory was effective, but nothing executes otherwise.

Proposed Feature:

Allow setting the laravel subdirectory as the basePath for the laravel extension.

First time opening an issue so feel free to shred me :)

[ricdizio]

This is a very nice feature to have. Because the way our projects are structured, Laravel is not always the root folder of our projects. This will be very helpful for those cases 👍

[daronspence]

The same idea applies for multi-project monoliths. We have 6~ laravel projects in one repo that share custom composer modules (also in the same repo). It would be nice if we could run multiple projects in one window and that the parser would be smart enough to start at the current file and navigate up the file tree to find the most relevant configuration.

[dir]

+1, noticed that this doesn't work in a monorepo setting due to it's checks here

vs-code-extension/src/support/php.ts

Lines 112 to 113 in fe8691e

	const hasVendor = projectPathExists("vendor/autoload.php");
	const hasBootstrap = projectPathExists("bootstrap/app.php");

vs-code-extension/src/support/php.ts

Line 121 in fe8691e

throw new Error("Vendor autoload not found, run composer install");

If those paths could be configurable it would be wonderful!