Skip to content
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

Add --no-cache to psalm commands #52

Open
boesing opened this issue Oct 10, 2023 · 3 comments
Open

Add --no-cache to psalm commands #52

boesing opened this issue Oct 10, 2023 · 3 comments

Comments

@boesing
Copy link
Contributor

boesing commented Oct 10, 2023

Hey there,

I recently stumbled upon a problem which I wanted to fix. I debugged stuff, etc. and while debugging I was using --no-cache and was unable to reproduce the problem. I then found out that psalm is executed without --no-cache here which is kinda problematic in some cases (i.e. when using codecept run --fail-fast which keeps the _run directory).

I'd like to propose adding --no-cache to the psalm CLI execution command so that there are no sideeffects from whatever caches.

@weirdan
Copy link
Member

weirdan commented Oct 10, 2023

I think that would be fine if it's configurable. Some plugins have a ton of tests that benefit from a cache being enabled.

@boesing
Copy link
Contributor Author

boesing commented Oct 10, 2023

Are the _run files generated by codeception do always have the same hashes?
But besides that, I would be fine with having that configurable 👍🏼

@weirdan
Copy link
Member

weirdan commented Oct 11, 2023

The filename hash is based on the file contents, but any dependencies from vendor can still be cached.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants