feat: enhance dry run diff view to show friendly names (resolves #51)#53
feat: enhance dry run diff view to show friendly names (resolves #51)#53Tiya22gif wants to merge 1 commit into
Conversation
|
I need a screenshot of the execution of the diff function , and it seems you have edited the unit test but didn't mark it in the pull request |
|
Thanks for the review @DotDev262 ! I’ll add a screenshot/log of the You’re also correct about the unit tests — I updated the existing tests to match the new friendly-name output format, but I forgot to explicitly mention that in the PR checklist/comment. I’ll update the PR description to reflect the test modifications clearly. |
|
The screenshot is not the output of the diff function rather its the dotnet build |
|
Okay, please give me some time @DotDev262. I hadn’t taken screenshots earlier, so I need to re-run and verify the diff output again. After that, I’ll upload all the required screenshots/logs and update the PR details accordingly. |
|
Any updates ? |

Related Issue
Closes #51
Proposed Changes
Engine.PrintDiffAsyncto use a newly implementedFormatFriendlyNamehelper.GetFriendlyNameinSystemSettingsServiceandISystemSettingsServiceto resolve raw registry paths into friendly internal catalog keys (e.g.,dark_mode,taskbar_alignment).App (winget): vscode.EngineTest.csto match the newly implemented friendly string formats.Example output now shows:
System Setting: show_file_extensionsApp (scoop): gitRegistry Tweak: HKCU\Software\WinHomeTest -> TestValueI also updated the existing unit tests to validate the new diff output formatting.
Type of Change
Screenshots / Logs (if applicable)
Testing & Verification
dotnet testand all 60+ cross-platform tests passed.GSSOC 2026 Checklist
dotnet format).gssoc:approvedlabel for this PR to count for points.