Replies: 2 comments 1 reply
-
Hi, each of your project should have its own You might also find this useful (phpstan/phpstan-src@518b20d) - you don't have to set whole different tmpDir, just the result cache path... |
Beta Was this translation helpful? Give feedback.
1 reply
-
I agree with this. It's very annoying to maintain two phpstan.neons when you have multiple worktrees of the same project. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi,
what do you think of using project specific temp sub dirs? Instead of having everything in
/tmp/phpstan
per default, the cache might be then in/tmp/phpstan/<project-name>
per default (if we have the <project-name> info).I'm aware that
tmpDir
can be configured but before doing that for each project/library I wanted to feel out if a more general solution might benefit others as well.My use case is that I'm mostly working on multiple projects/libraries in parallel and when I run phpstan in project a and then in project b the second run invalidates the cache of the first run (if I understood it correctly, at least that's the symptom I seem to be experiencing).
And to make things worse (but that's our problen :)) we have a project that currently has 2 composer.json files and I also have 2 phpstan dirs in that project and run them both via commit hook where each run invalidates the cache of the other so I do not benefit from caching at all.
Does this make sense, would you except a PR for this?
Beta Was this translation helpful? Give feedback.
All reactions