Project60 / Project60/org.project60.banking
Matching memberships based on purpose
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 22
- Forks
- 45
- Avg merge
- 3d 15h
- Merged PRs (30d)
- 7
Description
As I understand it, currently btx are matched to memberships based on amount and date. In my NGO we have various memberships with free-range amounts. If a contact has two such memberships, this creates a problem. I would like to match memberships based on btx.purpose using a regex for example.
Contributor guide
No contributing guide indexed for this repository
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
No files, tests, or entry points are named. Start by tracing the existing membership matching flow that compares transaction amount and date, then determine how btx.purpose and a configurable regular expression should participate. Done means distinct free-range memberships can be matched reliably by purpose, with behavior for invalid or non-matching expressions established.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 20/100