tldr-pages / tldr-pages/tldr-python-client
Feature Request: completely & precisely control cache and remote resource request
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 749
- Forks
- 117
- PR merge metrics
- No merged PRs in 30d
Description
I am making a wrapper of this tldr client to display default & private tldr pages at the same time, but it is confusing to config whether to use cache.
Sometimes I do not want cache and only want remote request. I set env TLDR_CACHE_ENABLED=0, it will still fall back to cache when web request fails, the cache can not be disabled completely.
On other times I only want to read from cache but do not want any remote request. I can not find an option to do this.
I have to do a lot of workaround. It might be good if these things can be controled completely & precisely.
Thank you!
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the client’s cache handling and remote resource request paths, then compare how TLDR_CACHE_ENABLED currently affects fallback behavior. Done means providing clearly defined controls for remote-only, cache-only, and existing fallback modes, with tests covering each mode.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100