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

Strategy for invalidating the cache when package variables change. #41

Closed
jimhester opened this issue Jan 24, 2015 · 1 comment
Closed
Labels
bug an unexpected problem or unintended behavior feature a feature request or enhancement

Comments

@jimhester
Copy link
Member

The global variables lintr looks for variables defined in the current package, however if lintr is run before the function or variable is defined, then it is defined later the cache needs to be invalidated and re-linted so that the new variable is picked up.

Maybe the easiest thing to do is just never cache expressions that produce this specific lint...

@jimhester jimhester added bug an unexpected problem or unintended behavior enhancement labels Mar 5, 2015
@jimhester jimhester added feature a feature request or enhancement and removed enhancement labels May 17, 2018
@MichaelChirico
Copy link
Collaborator

I'm going to close this -- it hasn't gotten any traction and there's no associated reprex. Jim, feel free to re-open if you plan to work on it / can share a reprex. Otherwise we can wait for a user to report the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug an unexpected problem or unintended behavior feature a feature request or enhancement
Projects
None yet
Development

No branches or pull requests

2 participants