-
-
Notifications
You must be signed in to change notification settings - Fork 76
Skip update when page not found #364
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
Skip update when page not found #364
Conversation
Co-authored-by: marchersimon <[email protected]>
…eComputing/tldr-node-client into skipUpdateWhenPageNotFound
…teWhenPageNotFound is set".
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @MDecker-MobileComputing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
slight tweaks on wording, otherwise looks fine.
Co-authored-by: Matthew Peveler <[email protected]>
Co-authored-by: Matthew Peveler <[email protected]>
@MasterOdin @owenvoke can we merge this? |
@marchersimon, I think so. I just left it as I don't really maintain the Node client. |
I think I was against this feature in the first place 😛 But now that it's there, we have obviously landed with a config knob to disable this. Thanks for the reviews everyone. |
When will a new version of |
I will have to publish it. But if you want to have it urgently, you can fetch from master by passing the git commit. |
Description
Introduced new configuration variable
skipUpdateWhenPageNotFound
forconfig.json
or.tldrrc
. When this variable is set totrue
, then upon a cache miss no (lengthy) cache update will be performed (on slower machines like a Raspberry Pi this update can take more than four minutes).Checklist
Please review this checklist before submitting a pull request.
npm run test:all
)