Joel Bennett

It's worth pointing out that [PowerShellGet v3](https://github.com/PowerShell/PowerShell-RFC/pull/185) is already in progres and doesn't intend to remain fully backward compatible @loic-sharma -- perhaps (assuming it uses the new v3 APIs, since...

@softlion except that PowerShell Core is backward compatible, and still ships the same old (v2) NuGet-based PowerShellGet dependency manager, so it doesn't change anything in this regard...

Yeah, I've been having this same problem. I've been gradually tweaking the configuration of the bridge, but even if I make changes in `values.yaml` and `upgrade` the whole chart, if...

I'm fairly certain we'd all be content with a "Statement" property instead ...

Yeah, _clearly_ it would be a great thing if Importing a module automatically included Cmdlet-derived classes as commands. But that circles around to `Import-Module` _and also_ `using module` -- needing...

Given that PowerShell already uses `$env:XDG_DATA_HOME/powershell` which defaults to `$HOME/.local/share/powershell` on Linux ... ### Can we just let PowerShell on Windows support `$env:XDG_DATA_HOME` too? PowerShell could just silently fall back...

So **WITH NO NOTICE** a bunch of code was broken that customized error and verbose output colors, and **there is now no way** to customize them in a **compatible** fashion,...

This did not (and does not) need to be one or the other. The new thing _could have_ been implemented on top of the old. If you implement it as...

I think going one way would probably be good enough. I mean, I have code for converting from 16bit colors to 16 colors.

> Actually, there's a problem with your proposal. `$Host.PrivateData` is managed by the host (ConsoleHost, EditorServices, etc...), so every host would have to adopt that pattern. `PrivateData` is just a...