PowerShell / PowerShell/PSResourceGet
New-PSScriptFileInfo/Update-PSScriptFileInfo -RequiredModules could accept string collection
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 576
- Forks
- 114
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 7
Description
Summary of the new feature / enhancement
when adding Required Modules to script, both New-PSScriptFileInfo and Update-PSScriptFileInfo require module references to be hashtable. It would be much easier to add only module names as strings.
This is supported by PowerShellGet module cmdlets.
Proposed technical implementation details (optional)
This syntax is currently required by PSResourceGet
Update-PSScriptFileInfo -path test.ps1 -RequiredModules @{ModuleName='module1'}, @{ModuleName='module2'}
This is the way, how PowerShellGet allows it:
Update-ScriptFileInfo -path test.ps1 -RequiredModules module1, module2
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 from the New-PSScriptFileInfo and Update-PSScriptFileInfo parameter handling and compare the shown PowerShellGet syntax with the current PSResourceGet behavior. Done means both cmdlets accept collections of module-name strings while continuing to support the existing hashtable form.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, powershell
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100