Open Manifest's Homepage in default browser via a command
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
Start by reviewing the existing winget show command and how it exposes the manifest homepage URL. Define the new homepage command around the requested manifest argument, opening a found URL in the system default browser and reporting when no homepage is present. Done means both behaviors are covered and the command is documented.
Written by the indexing model from the issue text.
Description
Description of the new feature/enhancement
I was expecting to have a command that would open the homepage of the manifest without having to use copy paste within the command window itself.
Current Process I have to employ
exploring winget's : List of available manifests via
winget show
The above command lists all the manifests.
looking through the manifests some may interest me and I run
winget show <app.mainfest>
This outputs the data of the manifest in a human readable form.
Its at this point i have to Select the URL of the homepage and copy paste it into my browser.
I was expecting to find an option to open the Homepage URL via the command line.
Proposed technical implementation details (optional)
I was epxecting to be able to type something like
winget homepage <app.manifest>
Expected Functions of this command.
- This command would [if homepage or other URL, is found in the manifest] take the url and open the url in the user's/systems default browser.
- If the homepage is not present in the manifest the output would notify the user the URL was not found in the manifest.
Example: Scoop home would open the app's homepage listed in the manifest allowing for exploration.
Additional Consideration
I would also consider making at least one informatic URL (be it license[licenseURL], privacy policy[not found in manifest], or homepage url[Homepage]) required in the minimum required.
- Dominant language
- C++
- Stars
- 26.4k
- Forks
- 1.8k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 15
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.
More from microsoft/winget-cli
-
Issue-Docs Possible-Duplicate
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
microsoft/winget-cli#6493 · 1 comment ·
-
Issue-Feature
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
microsoft/winget-cli#6427 ·
-
Issue-Feature
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
microsoft/winget-cli#6397 ·
-
Issue-Feature
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
microsoft/winget-cli#6396 · 1 reaction ·
-
Issue-Feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
microsoft/winget-cli#6394 · 1 comment ·
All issues in microsoft/winget-cli
Similar issues
-
Website Doc Typo Open
Difficulty 1/5 Under an hour Newbie friendliness 92/100
-
Difficulty 1/5 1-3 hours Newbie friendliness 92/100
autowarefoundation/autoware_universe#13413 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
automated-analysis bug memory-safety
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100