feat(donations): donation history, CSV export with Bull queue, and fund release#283
Open
dDevAhmed wants to merge 3 commits into
Open
feat(donations): donation history, CSV export with Bull queue, and fund release#283dDevAhmed wants to merge 3 commits into
dDevAhmed wants to merge 3 commits into
Conversation
…ease
- Issue 261: GET /campaigns/:campaignId/donations - paginated donor leaderboard
sorted by amount desc, 20 per page, anonymous donations masked via isAnonymous
field, returns rank/walletAddress/amount/assetCode/createdAt/txHash
- Issue 262: GET /users/me/donations - personal donation history for authenticated
user, filterable by campaignId/startDate/endDate, sortable by amount or
createdAt, includes campaignTitle/campaignStatus/txHash per donation
- Issue 263: GET /users/me/donations/export - CSV export with columns Campaign,
Amount, Asset, Date, Tx Hash, USD Equivalent; exports over 500 rows are
processed asynchronously via Bull export queue with job-status polling at
GET /users/me/donations/export/:jobId/status
- Issue 272: POST /campaigns/:campaignId/milestones/:milestoneId/release -
fund release request for UNLOCKED milestones, creator-only, records
signaturePayload, validates amount <= milestone target, prevents duplicate
PENDING releases; legacy /fund-releases path preserved for compat
Schema changes:
- Add isAnonymous Boolean field to Donation model
- Add UNLOCKED to MilestoneStatus enum
- Add FundReleaseStatus enum and FundRelease model
- Remove overly-restrictive unique([milestoneId, campaignId, creatorId])
constraint on FundRelease to allow re-requests after cancellation
Queue changes:
- Add QUEUE_EXPORT constant and register export queue in QueueModule
- Add ExportProcessor (@processor) for async donation CSV generation
- Register export queue in Bull Board (dev admin UI)
…nation-history-fund-release feat(donations): donation history, CSV export with Bull queue, and fund release
|
@dDevAhmed Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits. You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Implements four related features covering donation history visibility, personal donation tracking, CSV export with async queue support, and milestone fund release requests.
What Changed
Issue 261 — Campaign Donation Leaderboard
Issue 262 — Personal Donation History
Issue 263 — CSV Export with Bull Queue
Issue 272 — Request Fund Release
Schema Changes
Why
These four issues form a cohesive donation-transparency and fund-management surface. They were implemented together to share schema migrations and avoid multiple PRs touching the same models.
Testing Performed
Risks Considered
closes: #261
closes: #262
closes: #263
closes: #272