Stu
Perhaps the code to get the php executable from the settings should also check if these 2 external settings exist and are set? Taken from the original issue #57. ```...
The order of precedence of finding the PHP executable in the settings is as follows: 1. `php.validate.executablePath` - VSCode's PHP Language Features 2. `php.executablePath` - Devsense's PHP Tools 3. `phpsab.phpExecutablePath`...
Not currently working on the GitHub Linux Codespace. Needs some more time to debug.
Ok, after figuring out I was supplying the the extension with the real path of the php (which broke things) instead of the symlink alias path, I can confirm that...
Ok, after figuring out I was supplying the the extension with the real path of the php (which broke things) instead of the symlink alias path, I can confirm that...
@valeryan Looking at some of the previous release tags, the format was `v.0.0.[version]`, however the `npm version` command says the `v.0` format is invalid. I suggest we continue to drop...
@valeryan could you double check the remaining issues from Copilot's review, I'm not sure if these changes need to be made or not.
@valeryan ok, thanks. it does seem to work on my test repo, but copilot is complaining about security or something, so not sure about it.
> Did you know you can't fork you own project. @valeryan Yeah I know, I tried the other day and it wouldn't let me even with a new name. It's...