Open shyim opened 7 months ago
it can be solved with:
"php.problems.exclude": {
"vendor/": true,
"vendor-bin/": true
}
I am fine when you want to close this, an another way could be still that globally jetbrains stubs files are ignored :thinking:
Thank you for reporting the issue.
We should be already ignoring problems in "vendor
" folder (and also caching the packages in there). So php.problems.exclude
should not be necessary.
But we're not treating custom "bin"
configuration properly - is that how you create the vendor-bin
folder?
EDIT: it's "config": { "bin-dir": ... }
which we ignored.
Will be fixed!
It's not a composer thingy, it's https://github.com/bamarni/composer-bin-plugin
We have some tools installed in a separate vendor-bin, to not conflict with our general packages.
Here our example :) https://github.com/shopware/shopware/tree/trunk/vendor-bin
@shyim I see! nice :) So:
"php.problems.exclude"
setting is a correct quick workaround"extra": { "bamarni-bin": { "target-directory": "vendor-bin", } }
configurationI would check that this composer package is installed, and then use vendor-bin
or it's overridden by
{"extra": { "bamarni-bin": { "target-directory": "vendor-bin", } }
to really catch anything :)
btw: thanks for building this!
Thank you for the suggestions, I'm glad I can help.
Hey,
some tools require jetbrains/phpstorm-stubs like roave-backward-compatiblity-check or phpstan.
These libraries in the vendor produce errors for the projects like this one: