microsoft / microsoft/winget-pkgs
[New Feature]: Validate against Portable Command Collisions
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 11.1k
- Forks
- 9.7k
- Avg merge
- 1h 32m
- Merged PRs (30d)
- 376
Description
Related to #16576 and #36752
With Portable apps being available in the Repo, it is foreseeable that at some point, two different applications will attempt to use the same command alias.
The CLI should already protect the user against this by not modifying the symlink if the target file is different (needs verification?)
With Zip packages coming soon, there will be support for multiple portable apps as a suite inside of the Zip package. Each of these apps receives their own command alias. This increases the chances that two portable apps will have the same command.
There should be some form of warning, and possibly even an error, when a package is submitted that would introduce a command alias conflict.
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
Review related issues #16576 and #36752, then inspect the CLI's portable-app alias handling and package-submission validation; the issue provides no file or test names. Done should be a defined warning or error when a submitted package introduces a command alias collision, with behavior verified for differing targets and Zip suites.
Written by the indexing model from the issue text.
Assessment
- Domain
- cli, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100