Justin Grote

@iSazonov as a proposal: ## Verbose ### Request Example `VERBOSE: WebRequest GET https://api.mysite.com/Users with 3KB application/json payload` (Query parameters removed if present, will be shown in Debug) ### Response Example...

Note that my summarizations above of the `Verbose` are mostly to "redact" sensitive information from Verbose, since Security WG said that info needed to be behind `Debug`, but this is...

> > Note that my summarizations above of the Verbose are mostly to "redact" sensitive information from Verbose, since Security WG said that info needed to be behind Debug Reasonable,...

> @JustinGrote it would be nice to see an engine event generated with the debugging information when -Debug is passed. > This would enable much more powerful debugging of the...

@iSazonov I will likely have some time to work on it this weekend, thank you. And yes for future readers, I should have been more clear that my request for...

@iSazonov on "community day" did you mean the PowerShell community call or the PowerShell team "community day" which I believe is monday where they focus on community issues. Is there...

@TobiasPSP Thank you. There is a pending issue with a duplicate httprequest reference I need to fix, and then it should be ready to merge, I'm hoping to have time...

https://github.com/PowerShell/PowerShell/pull/25510 is complete, has passed all tests, and has been reviewed by @iSazonov. @TobiasPSP @iSazonov @SydneyhSmith @SteveL-MSFT any further review required before merge?

I agree `&!` is the more intuitive way to go for those coming from other shells, however in super-duper-linter I am usually running native commands by building a parameter array...

@oising well for one, that command doesn't work because you have to preface it with the command you want to run, are you suggesting adding the functionality?  This kinda...