microsoft / microsoft/winget-studio
Provide lower level command details
Open
Nobody has claimed this yet.
Issue-Feature
- Dominant language
- C#
- Stars
- 67
- Forks
- 15
- PR merge metrics
- No merged PRs in 30d
Description
Description of the new feature / enhancement
Provide a way for a user to see the code being executed (or at least a proxy of the commands if WinGet COM APIs are called).
For example, Get, Set, Test, and "Export" should be things one could execute directly against dsc.exe.
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 by tracing how the Get, Set, Test, and Export operations are handled, then examine the integration points for dsc.exe and WinGet COM APIs. The work is done when users can inspect the underlying commands or a documented proxy for each operation, with behavior verified for all four operations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100