Skip to content

Conversation

@raxod502
Copy link
Contributor

@raxod502 raxod502 commented Jun 11, 2025

Handle part of #1936 by allowing for M-x projectile-invalidate-cache to still clear the global cache even if the user invokes it from outside of any project, and no longer force the user to select a project to invalidate the cache for in that case. Also, document how this command may be used for troubleshooting.


  • The commits are consistent with our contribution guidelines
  • You've added tests (if possible) to cover your change(s)
  • All tests are passing (eldev test)
  • The new code is not generating bytecode or M-x checkdoc warnings
  • You've updated the changelog (if adding/changing user-visible functionality)
  • You've updated the docs (when adding new project types, configuration options, commands, etc)

@raxod502
Copy link
Contributor Author

I haven't added tests since this is a fairly small logic change and there aren't existing tests for projectile-invalidate-cache, so I'm not sure offhand what if anything would need to be mocked, but if it is desired, I can look into it and figure it out.

@raxod502
Copy link
Contributor Author

The snapshot tests appear to also be failing on master, so let me know if I should look at those as well.

@bbatsov bbatsov merged commit 0da5973 into bbatsov:master Jun 12, 2025
4 of 5 checks passed
@bbatsov
Copy link
Owner

bbatsov commented Jun 12, 2025

Thanks!

Seems the tests are failing because of some upstream deprecations - I'll handle those myself.

@raxod502 raxod502 deleted the rr-invalidate-cache branch June 12, 2025 19:54
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

Successfully merging this pull request may close these issues.

2 participants