Thomas Nieto

What is the use case for doing it this way? Can't you just have that parameter in just the required parameter set?

I could see this as its own key in `PSData` of the obsolete module. Then the gallery and installing the module could say this module is deprecated and the replacement...

@kilasuit That linked proposal was that the replacement module would have the metadata saying which module it replaced. The concern from the WG is that during command discovery / module...

@SydneyhSmith if this issue could be fixed before the next preview release that would be awesome.

It helps but still doesn't solve the usability issue defined in #1247. One of my use cases would be people installing my `AnyPackage.PSResourceGet` module from PowerShellGet v2 which would still...

@JustinGrote 1. I like the idea of adding `Find` operator to support the `Plan` parameter. 2. Did the prompt come from AnyPackage or ModuleFast? Also what was the `$ConfirmPreference` set...

Find-Package support was added in the latest release (v0.1.2)

@SydneyhSmith because PowerShell best practices is to use a default value over a required parameter when a reasonable default value can be derived from expected use. I would think a...

@bergmeister / @SydneyhSmith why was this closed?

@SydneyhSmith is there a way we can get ps1xml files to have syntax highlighting (XML) on the gallery?