Patrick Meinecke

> Anyway I think there might be at least some basic support for Add-Type handling without state considered. At least for the cases where it is explicit condition-less statement. Unfortunately...

Converting to a discussion since it's not something strictly actionable in this project itself.

I can say with certainty it's not a bug. I can only guess at the reason behind it, but [Martin's guess](https://github.com/PowerShell/PowerShell/issues/25655#issuecomment-2973316656) of "keeping it simple/consistent" seems right. For documentation, you...

There's already an option to ignore it if you really want to, aliases do not trigger the warning. Nor do functions without a `-`. I think the argument about `Sort`...

> This is exactly what I mean "_the end justifies the means_", meaning that the **forced** _recommendation_ leads to even poorer practices: Yeah, it feels kind of dirty, users might...

You can get there today by doing this: ```powershell function PSConsoleHostReadLine { [Microsoft.PowerShell.PSConsoleReadLine]::ReadLine($Host.Runspace, $ExecutionContext) preprompt | Out-Null } ``` That'll have the same limitations that in-engine support would have. Aside...

> A way to _lessen_ this pollution would be to offer a way to _redraw the prompt string in place_: > Say you submit `Get-Date` at prompt `PS C:\>` and...

> Any updates on this? > > As a former Windows user and admin who now works on unix, I'd love to get back to using PowerShell. However, not having...

The Engine WG discussed this, we do not think this meets the bar for impact and we're marking this issue as declined.

@nohwnd Here's the demo I posted the other day  Still some things to iron out yet, but it's coming along.