PowerShell / PowerShell/PSResourceGet
Local cache for repository lookups
Open
Nobody has claimed this yet.
Area-PSRepository
feature_request
- Dominant language
- C#
- Stars
- 576
- Forks
- 114
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 7
Description
Summary of the new feature / enhancement
Like previously suggested, but closed due to "not until we've released v3.0":
- 2022-02-21: https://github.com/PowerShell/PSResourceGet/issues/613
- 2022-05-24: https://github.com/PowerShell/PSResourceGet/issues/653
- https://github.com/PowerShell/PowerShell-RFC/pull/237/changes#diff-3543dd227ba0e5d6aa1adb426c03d460807134ca378489b072e91e5c4dda2845R342-R379
Proposed technical implementation details (optional)
No response
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
Start by reading the linked issues 613 and 653 and the referenced PowerShell RFC pull request 237. No implementation files, tests, or specific lookup entry point are identified, so first determine the repository-lookup paths and the intended cache behavior; done should mean repository lookups use the agreed local cache semantics.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100