Suggestion: Offer to cache templates rather than fetching latest versions
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 816
- Forks
- 230
- Avg merge
- 6h 4m
- Merged PRs (30d)
- 1
Description
It could be that I am using the CLI incorrectly (not using some better paradigm) but most CLI tools that I use (aws, git, and others) store at least a "rc" or other config file in my home directory for common/global configuration options. It would also make sense to stick a local copy of the template directory there, rather than scattering them all over my filesystem when I make new functions.
I think this would help me reduce repetition when I use the CLI (as I could reference a profile in the rc file) and could cache templates. Thoughts?
Contributor guide
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
No files, tests, or entry points are named. Start by locating the CLI's template-fetching and configuration handling, then determine how global profiles and cached templates should interact. Done would require an agreed configuration and cache design, implementation, and tests covering template reuse and updates.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli, developer-experience
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100