microsoft / microsoft/winget-cli
Configuration PowerShell objects do not expose full data
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 26.4k
- Forks
- 1.8k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 15
Description
Brief description of your issue
The configuration PowerShell cmdlets do not always return the full objects that wrap their COM counterpart calls. All of the properties should be exposed so that callers of the PowerShell cmdlets can use them fully.
For instance:
- Units are not exposed on the configuration set
- The result object of applying a configuration set is only the HRESULT, not the full result object including the individual statuses
A full pass should be done to ensure that it is possible to fully inspect these objects.
Steps to reproduce
Use configuration cmdlets.
Expected behavior
Get full data.
Actual behavior
Get partial data.
Environment
Current code.
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 with the configuration PowerShell cmdlets and the COM counterpart calls they wrap. Compare the configuration set properties and the result returned when applying a set, including individual statuses. Done means callers can inspect the full data exposed by these configuration objects rather than only partial properties or an HRESULT.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, powershell
- Domain
- api, cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100