microsoft / microsoft/winget-studio
DSC error short description should not include warnings
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 67
- Forks
- 15
- PR merge metrics
- No merged PRs in 30d
Description
Description of the new feature / enhancement
When a DSC operation fails, the error notification contains too much verbose information, in particular the DSC warnings as well. The description of the error should not include warnings from DSC output
Steps to reproduce
- Go to validate a resource page
- Enter
Microsoft.WinGet/Packageand clickGetoperation - The operation fails as no ID is provided, but the UI notification is too noisy to appropriately communicate this to the user
Actual Behavior
See screenshot (Click to open)
Expected Behavior
We should have a parser for DSC output which is currently a string result and separate warnings from errors
See screenshot (Click to open)
Proposed technical implementation details
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the validate resource page and follow the DSC operation handling for the Get operation described in the reproduction steps. Inspect where the DSC string result becomes the error notification; done means DSC warnings are separated from the error so the notification communicates only the failure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100