PowerShell / PowerShell/PSResourceGet
feature request (breaking) - fail on get/find
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 576
- Forks
- 114
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 7
Description
(referencing PowerShellGet 2.0)
Please consider changing behavior when Get-Module or Find-Module does not find anything.
Get-Package and Find-Package both fail, enabling the decent usage of try/catch and other errorhandling options
Get-Module or Find-Module both return nothing, but do not fail.
However, for instance Get-InstalledModule does fail....
This is inconvenient and inconsistent.
I noticed in issue https://github.com/PowerShell/PowerShellGet/issues/335 that v3 might introduce a new command?
And while on subject; same with the usage of -Source and -Repository params......
Nice moment to align...
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 comparing the behavior of Get-Module, Find-Module, Get-Package, Find-Package, and Get-InstalledModule when no results are found. Review the referenced PowerShellGet issue 335 and the current -Source and -Repository handling. Done means the intended failure behavior and parameter alignment are decided and consistently covered for the affected commands.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100