I have found what seems to be a bug. I have a PHP project developed in VSCode 1.44.1 (using Remote Containers [https://code.visualstudio.com/docs/remote/containers]), and using Makefile for the build process. So Task Explorer looks ideal (and it is!). Task Explorer 1.26.3.
I have configured Task Explorer to exclude vendor/ and bin/.phpunit because they contain some Makefiles and ant files in a workspace .vscode/settings.json:
At first, it works as expected and shows the make targets of my Makefile (notice that in this very moment, the exclusion is still irrelevant because such directories do not even exist):
Then, I download the dependencies so vendor/ is populated; and run the phpunit tests to bin/.phpunit is populated, and TaskExplorer shows too much tasks:
Ugly. I restart VSCode and the wrong makefiles disappear again :-)
Cool again. I can live with it, but I wanted to report it.
Hi,
I have found what seems to be a bug. I have a PHP project developed in VSCode 1.44.1 (using Remote Containers [https://code.visualstudio.com/docs/remote/containers]), and using Makefile for the build process. So Task Explorer looks ideal (and it is!). Task Explorer 1.26.3.
The project is open source and can be use for testing the bug here: https://gitlab.com/javier.sedano/vaca/-/tree/master
I have configured Task Explorer to exclude vendor/ and bin/.phpunit because they contain some Makefiles and ant files in a workspace .vscode/settings.json:
At first, it works as expected and shows the make targets of my Makefile (notice that in this very moment, the exclusion is still irrelevant because such directories do not even exist):
Then, I download the dependencies so vendor/ is populated; and run the phpunit tests to bin/.phpunit is populated, and TaskExplorer shows too much tasks:
Ugly. I restart VSCode and the wrong makefiles disappear again :-)
Cool again. I can live with it, but I wanted to report it.