-
Notifications
You must be signed in to change notification settings - Fork 19
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 a Cache #60
Comments
Sounds good to me. |
tgetgood
added a commit
to tgetgood/name-your-contributors
that referenced
this issue
Jan 1, 2018
tgetgood
added a commit
to tgetgood/name-your-contributors
that referenced
this issue
Jan 11, 2018
tgetgood
added a commit
to tgetgood/name-your-contributors
that referenced
this issue
Jan 11, 2018
🎉 This issue has been resolved in version 3.4.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
To daemonise effectively (regarding #48) we need a local cache on disk. Nothing fancy just hashes of the queries and timestamps. Global ttl.
This will also have a beneficial impact on development, and in normal use it will mean that if a query fails because it's too expensive (not in daemon mode) then the data grabbed does not get thrown away when you try again later.
The text was updated successfully, but these errors were encountered: