[Subscription] Improve detection logic
Open
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 871
- Forks
- 140
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 201
Description
Will enable https://github.com/hackclub/hcb/issues/10680, https://github.com/hackclub/hcb/issues/10725, and not require receipts for recurring same-amount transactions
We will tackle this after implementing the new Ledger model, which can be used to collect a list of transactions for a subscription.
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
Read linked issues #10680 and #10725, then inspect the new Ledger model when it is available to understand how subscription transactions are collected. Done means detection enables those cases and does not require receipts for recurring same-amount transactions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- backend, databases, payments
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100