-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cache directory is causing issues with some IDE's code inspection #8
Comments
Another approach is to define the cache folder explicitly when initializing FunctionMocker // in your tests bootstrap file
FunctionMocker::init(['cache-path' => '/temp']); |
With 7+ plugins in the same project, it's a bit hard to set all the exclusions. I've tried the last approach using something like I've also tried different ways to pass a temporary directory, such as reading the All these solutions lead to the same result:
I don't see where Patchwork or FunctionMocker are involved in the stack trace, but going back to |
I can reproduce the issue on |
Further investigation led me to believe this is something Function Mocker inherits from Patchwork; I will look more to make sure and document my findings. |
+1. I have the same problem on PHPStorm, I have a number of plugins in my project and I suffer from inspection issues, too many definitions. When can we expect something? |
I've noticed that in the most recent version of the library, a
vendor\lucatume\function-mocker\cache\
folder is created and some cached code is saved there.This is causing two issues:
Is it possible to make the library cache these files outside the project (e.g. in the default "temp" directory)?
A solution which requires an environment variable (so it can fall back to the current
vendor\lucatume\function-mocker\cache\
if the variable is missing) would be also fine.The text was updated successfully, but these errors were encountered: