Thomas Nieto
Thomas Nieto
This auto update feature is missing consideration for modules that follow semantic versioning in regards to major versions and breaking changes. I would not want auto update or a notification/warning...
Related issue about update notifications: https://github.com/PowerShell/PowerShellGet/issues/91
@SydneyhSmith why was this design chosen? This is bad design in my opinion and has inconsistent behavior when compared to core cmdlets. Warnings are insufficient because they are difficult to...
@SydneyhSmith / @alerickson any way we could get this fixed with PSGet 3.0?
@SydneyhSmith My recommendation would be to move all non-module shipped files out of the module directory so `Test-FileCatalog` will succeeded by default without any workarounds. To accomplish that the `PSGetModuleInfo.xml`...
@alerickson I found that `Get-Module` returns a `PSModuleInfo` with a `ResourceRepositoryLocation` property. You'll want to update this logic to flex the old or new file path. https://github.com/PowerShell/PowerShell/blob/8f37cced709168f313a00b2e3ee7088495bbcd7a/src/System.Management.Automation/engine/Modules/ModuleCmdletBase.cs#L2596-L2619
@alerickson yeah I can.
Yes, that is a workaround but does not match the help or v2 behavior.
@SydneyhSmith the error message does not indicate that behavior and resolution at all, and will need to be updated. Also, what happened to having a local cache of the resource...
If they're going to mimic behavior they should do the same thing that PowerShellGet v2 does. It doesn't require a mandatory parameter to return all items in the repository. In...