`purchase` paid apps
Nobody has claimed this yet.
- Dominant language
- Swift
- Stars
- 12.4k
- Forks
- 299
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 1
Description
Purchase paid (non-free) apps.
Maybe add a --purchase flag to mas install after #557 is resolved.
If someone tries to install a non-free app that wasn't previously purchased without including --purchase, output an error specifying the cost and the necessity to supply the --purchase flag.
To ensure that people don't spend more than they expect on an app, we could require user to specify a maximum cost they're willing to pay (like --purchase 10.00USD with a special --purchase unlimited value to specify no limit). We'd have to check how the store handles prices in different currencies. We would require that the specified currency match the currency expected by the MAS for the signed-in account for the purchase of the specified app.
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 reviewing the dependency on issue #557 and the existing mas install command. Investigate how the Mac App Store reports prices and account currencies, then define the purchase and maximum-cost behavior, including errors when --purchase is absent. Done means paid apps can be purchased safely with the specified limit and currency requirements.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- swift
- Domain
- cli, payments
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100