Remove absolute path check

[rugk]

Fixes #56

Untested, and as far as I see the spawn thing likely makes it impossible to use, i.e. it does not work as I want, does it?

So just consider this as a first try/starter for you. (I have no experience in VS Code development.)

[antedeguemon]

👍 on this.

I was getting the same Invalid executable path for caddy error in my environment (MacOS), and it turned out that I had caddyfile.executable set only as caddy (which is in my $PATH but is not an absolute path).

Updating the executable to /opt/homebrew/bin/caddy solved it. But IMO this check should be removed, as it even contradicts the default caddy executable behaviour, which is relative and not absolute.

vscode-caddyfile/packages/client/src/formatter.ts

Lines 34 to 43 in 9ba30fc

	if (executablePath !== undefined && executablePath !== null && executablePath !== '') {
	if (!path.isAbsolute(executablePath)) {
	vscode.window.showInformationMessage('Invalid executable path for caddy.');
	return reject();
	}
	executable = executablePath;
	} else {
	executable = 'caddy';
	}

It might also fix #307 that is affecting Windows users.