Handles Pest filters

[joedixon]

No description provided.

[amadeann]

@joedixon
I don't have pest installed, and when I try to run tests tests I get the following error:
c:/laragon/www/m_project_name/vendor/bin/pest.bat : The term 'c:/laragon/www/m_project_name/vendor/bin/pest.bat' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.

I am on Windows 11.

[amadeann]

When I remove pestphp/pest-plugin": true line from composer.json and reopen VS Code tests run again. Since pestphp/pest-plugin": true is a part of Laravel's default install, this will trip everybody up unless they use pest too. Maybe there is another way to detect if pest is in use?

[joedixon]

Hey @amadeann can you double check your composer.json?

The Pest binary will only be used if pestphp/pest is present.

[amadeann]

@joedixon
Yes, I have checked it. I had "pestphp/pest-plugin": true in config.allow-plugins, which is a part of laravel/laravel default composer.json (this line).

Once I removed that line, and reloaded VS Code, the plugin works as usual.

The problem is that this line:
const isPest = fs.readFileSync(composerJson, 'utf8').includes('pestphp/pest');

matches anything in composer.json file that contains pestphp/pest, even if it's just an allowed-plugin added by default in Laravel installer.

[joedixon]

@amadeann good catch. I'll submit a PR to make this check a little more explicit.

[joedixon]

@amadeann think this should do it: #138

[amadeann]

Works as before with the new version :)

[joedixon]

@amadeann to confirm, you mean before you ran into the issue? i.e. it's working as expected?

[amadeann]

@joedixon
Yes, works as expected with your fix from yesterday. Sorry it wasn't clear from my message.