microsoft / microsoft/winget-create
Arguments cannot be put in any order during `wingetcreate update`
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 651
- Forks
- 114
- Avg merge
- 7h 52m
- Merged PRs (30d)
- 3
Description
Brief description of your issue
You have to use the arguments passed to wingetcreate update in a specific order or you get an error, which isn't reflected in the documentation.
Steps to reproduce
- Decide you want to update a manifest.
- Run
wingetcreate updateand look at the options you have to pass (note that--versionis listed before--urlsin that help section). - Decide to do it that way, and run something like
wingetcreate update -v 5.3.2 -u https://d13g8g4x8s9rc1.cloudfront.net/downloads/files/cdn/ti-nspire/5.3.2/TINspireCXStudentSoftware-5.3.2.129.exe TexasInstruments.TI-Nspire - Become confused as it doesn't work even though it should since you passed valid arguments.
Expected behavior
You get a manifest that is ready to be committed or used locally.
Actual behavior
You get an error stating "A required value not bound to option name is missing.", even though according to the help, you've bound all of the options you needed to, just in a different order.
Environment
Windows Package Manager Manifest Creator v0.4.1.1
Any other software?
Microsoft Solitaire Collection version 4.10.7290.0.
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 reproducing the documented wingetcreate update -v 5.3.2 -u <URL> TexasInstruments.TI-Nspire command and inspect the wingetcreate update argument parsing and help entry point. Done means valid options work regardless of the order shown in the help, producing a manifest instead of the binding error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100