microsoft / microsoft/winget-cli
Set-WinGetUserSettings needs distinct parameters
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 26.4k
- Forks
- 1.8k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 15
Description
Description of the new feature / enhancement
The Set-WinGetUserSettings cmdlets takes a hashtable of user settings. I think it would follow better PowerShell practice to define each setting as a separate parameter. If the user has a hashtable, they can splat to the cmdlet. The current design puts a burden on the user when they only want to modify a single setting.
Proposed technical implementation details
Add parameters for settings like ProgressBar and UpdateInterval. I would even suggest creating a separate command to set experimental features.
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 locating the Set-WinGetUserSettings cmdlet and its current hashtable-based parameter. Review how settings such as ProgressBar and UpdateInterval are defined and handled, then clarify the scope of separate experimental-feature commands. Done means the requested settings can be supplied as distinct parameters while preserving supported hashtable splatting behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100