We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Specifying -Verbose on Out-ConsoleGridView produces base64-encoded strings like:
-Verbose
Out-ConsoleGridView
VERBOSE: TW9kZSRfLiJNb2RlV2l0aG91dEhhcmRMaW5rIg== VERBOSE: TGFzdFdyaXRlVGltZSRfLiJMYXN0V3JpdGVUaW1lU3RyaW5nIg== VERBOSE: TGVuZ3RoJF8uIkxlbmd0aFN0cmluZyI= VERBOSE: TmFtZSRfLiJOYW1lU3RyaW5nIg==
Culprit TypeGetter.cs#LL172C1
Decoding these produces:
'TW9kZSRfLiJNb2RlV2l0aG91dEhhcmRMaW5rIg==', 'TGFzdFdyaXRlVGltZSRfLiJMYXN0V3JpdGVUaW1lU3RyaW5nIg==', 'TmFtZSRfLiJOYW1lU3RyaW5nIg==' | ForEach-Object { [System.Text.Encoding]::UTF8.GetString([System.Convert]::FromBase64String($_)) } $ Mode$_."ModeWithoutHardLink" $ LastWriteTime$_."LastWriteTimeString" $ Name$_."NameString"
Verbose output should help the user track the behaviour of the cmdlet and diagnose any potential problems.
The user must decode the verbose output.
No response
0.7.2
The text was updated successfully, but these errors were encountered:
Hmmm... I'm not sure what folks would expect to see with -Verbose. Fixing the "culprit" to emit the Column name seems unsatisfactory:
A quick fix is to just remove this code. A bigger fix is to figure out what the right stuff to emit on -Verbose is.
@maxaddat, what would you expect to see?
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
Prerequisites
Steps to reproduce
Specifying
-Verbose
onOut-ConsoleGridView
produces base64-encoded strings like:Culprit TypeGetter.cs#LL172C1
Decoding these produces:
Expected behavior
Verbose output should help the user track the behaviour of the cmdlet and diagnose any potential problems.
Actual behavior
The user must decode the verbose output.
Error details
No response
Environment data
Version
0.7.2
Visuals
No response
The text was updated successfully, but these errors were encountered: