Set view does not show any result after completion

[mdanish-kh]

Brief description of your issue

If you invoke set operation on a resource via the DSC CLI, you'll get beforeState, afterState & changedProperties in the response. WinGet studio shows nothing in the Results view after the set operation completes successfully

Steps to reproduce

1. Go to validate a resource view
2. Type Microsoft.WinGetCreate/Settings for the resource name
3. The settings input is

settings:
  Telemetry:
    disable: true

4. Click on Set operation

Expected behavior

The results view should look like the output of dsc resource set -r "Microsoft.WinGetCreate/Settings" --input '{"settings": {"Telemetry": {"disable": true}}}'

beforeState:
  settings:
    $schema: https://aka.ms/wingetcreate-settings.schema.0.1.json
    Telemetry:
      disable: false
    CleanUp:
      intervalInDays: 7
      disable: false
    WindowsPackageManagerRepository:
      owner: microsoft
      name: winget-pkgs
    Manifest:
      format: yaml
    Visual:
      anonymizePaths: true
afterState:
  settings:
    $schema: https://aka.ms/wingetcreate-settings.schema.0.1.json
    Telemetry:
      disable: true
    CleanUp:
      intervalInDays: 7
      disable: false
    WindowsPackageManagerRepository:
      owner: microsoft
      name: winget-pkgs
    Manifest:
      format: yaml
    Visual:
      anonymizePaths: true
  action: Partial
changedProperties:
- settings

Actual behavior

WinGet studio shows nothing in the Results after completion

Environment

Windows: Windows.Desktop v10.0.26100.6899
System Architecture: X64
WinGet Studio version 0.100.302.0

[AmelBawa-msft]

JohnMcPMS, currently, the Set and Test unit APIs in the WinGet Configuration COM API don’t return settings output or property differences. Is that intentional because we can just call Get after Set, and Get before and after Test to see the changes and the diff?

[JohnMcPMS]

The API was designed well before DSCv3 and there has been no impetus to update it. While you can make those calls and attempt to diff yourself (DSCv3 does exactly this when you don't define a Test action), it doesn't always work. Adding it to the API would likely be acceptable as long as it was documented to not always be provided (DSCv2 would have to implement it synthetically if at all).