microsoft / microsoft/winget-cli
WinGet configure should look for a default config file if none is provided
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
I'm a lazy developer and like to type as few characters as possible. It would be great if I could just run the winget configure command from the root of a project folder and the configure command would find my default config and use it. Similar to how I can run the npm install command with Node applications and I don't have to specify a path to my package.json, or I can run dotnet build for .NET apps and I don't have to specify what project file to build (but I can if the defaults don't work for me).
Proposed technical implementation details
When a user runs winget configure in a folder:
- Look first for the default configuration file in
./configurations/configuration.dsc.yaml(following the recommended default file naming conventions) - If the default isn't found, behave the same as it does today
- -or- Even better would be to recurse down from the current directory, look for files named *.dsc.yaml (or *.dsc.yml) and then provide the user with a list of relative file paths for all the configuration files found. This would make it easy to copy/paste and run
winget configure -fwith one of the discovered files.
- -or- Even better would be to recurse down from the current directory, look for files named *.dsc.yaml (or *.dsc.yml) and then provide the user with a list of relative file paths for all the configuration files found. This would make it easy to copy/paste and run
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 winget configure command handling and trace how it behaves when no configuration file is supplied. Check the current file-selection path, then verify that ./configurations/configuration.dsc.yaml is discovered and used when present, while the existing behavior remains unchanged when it is absent.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100