PowerShell / PowerShell/PowerShellEditorServices
Introduce a new ModuleService for common module management operations
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 767
- Forks
- 266
- Avg merge
- 3d 16h
- Merged PRs (30d)
- 1
Description
I just implemented PowerShell Gallery module update logic for the PowerShell ISE Preview and realized that this behavior really should be made available to all editors which use Editor Services. I'd like to take the work @dfinke did for PowerShell Gallery module installation and put it together with my module update checking logic to make a new ModuleService which has the following features:
- List and install modules from the PowerShell Gallery (and any other registered repository)
- Check for, get notified about, and install modules that have new updates
- Publish a module to the PowerShell Gallery (generally used for publishing a module from the current workspace path)
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 reviewing the PowerShell Gallery module installation work by @dfinke and the PowerShell ISE Preview module update logic referenced in the issue. Compare those existing behaviors with the proposed shared ModuleService. Done means the service supports listing, installing, update checking and notification, updating, and publishing modules through registered repositories.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, powershell
- Domain
- backend-api-design, devtools
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100