`invoke-scriptanalyzer -fix -Confirm` should be more specific

Currently the -Fix -Confirm (and -WhatIf) common parameters aren't very specific on what and how PSScriptAnalyzer is about to correct the found violations:

invoke-scriptanalyzer .\Test.ps1 -fix -Confirm

Confirm
Are you sure you want to perform this action?
Performing the operation "Analyzing and fixing file C:\Users\Gebruiker\Scripts\Test\Rule\Test.ps1" on target "C:\Users\Gebruiker\Scripts\Test\Rule\Test.ps1".
[Y] Yes  [A] Yes to All  [N] No  [L] No to All  [S] Suspend  [?] Help (default is "Y"): n

I would expect a more specific message of what and how a violation is changed, e.g.:

invoke-scriptanalyzer .\Test.ps1 -fix -Confirm

Confirm
Are you sure you want to perform this action?
Changing "$pascalCase = 'Test'" to "$PascalCase = 'Test'" at line 10 character 5 of file  "Analyzing and fixing file C:\Users\Gebruiker\Scripts\Test\Rule\Test.ps1" on target "C:\Users\Gebruiker\Scripts\Test\Rule\Test.ps1".
[Y] Yes  [A] Yes to All  [N] No  [L] No to All  [S] Suspend  [?] Help (default is "Y"): n

Start by reproducing the invoke-scriptanalyzer command with -Fix and -Confirm, then locate the implementation of its confirmation handling. No file or test is named; done means the prompt identifies the specific violation change and its location, with coverage for the updated confirmation behavior.