microsoft / microsoft/winget-studio

Test resource view result does not show `desiredState`, `actualState`, `differingProperties`

Open
#150 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Issue-Bug
Dominant language
C#
Stars
67
Forks
15
PR merge metrics
No merged PRs in 30d

Description

Brief description of your issue

If you test a resource via the DSC CLI, you'll get desiredState, actualState & differentProperties in the response. WinGet studio shows the generic Get operation response in case of a Test operation result

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
  1. Click on Test operation
Expected behavior

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

desiredState:
  settings:
    Telemetry:
      disable: true
actualState:
  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
  action: Partial
  _inDesiredState: false
inDesiredState: false
differingProperties:
- settings
Actual behavior

The result view currently looks like

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

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

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the issue in the WinGet Studio resource view using the Microsoft.WinGetCreate/Settings input and compare the Test result with the dsc resource test output. Trace the Test operation result rendering and update the view so it displays desiredState, actualState, inDesiredState, and differingProperties; done when the result matches the documented expected output.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
desktop
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.