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
Summary of the new feature / enhancement
Currently,
Publish-PSResourceperforms a module manifest validation by runningTest-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-PSResourcevalidates a manifest file, but we should consider adding a common validation toSet-ModuleManfiestonce we have a custom validation function.Proposed technical implementation details (optional)
No response