PowerShell / PowerShell/PSResourceGet
Remove dependency on PowerShell Test-ModuleManifest from Publish-PSResource
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
Currently, Publish-PSResource performs a module manifest validation by running Test-ModuleManifest, but the test cmdlet is too strict and rejects valid manifests if required modules or root module path is missing from the machine. We should have a custom validation function that does can validate a standalone module manifest file outside the context of a fully installed and operational module.
Currently only Publish-PSResource validates a manifest file, but we should consider adding a common validation to Set-ModuleManfiest once we have a custom validation function.
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 at Publish-PSResource, where the current Test-ModuleManifest validation is used, and compare its behavior for manifests with missing required modules or root module paths. Define what standalone manifest validation must accept, then determine whether the common validation should also be used by Set-ModuleManifest; done means Publish-PSResource validates without requiring an installed operational module.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 32/100