[FEATURE] Generate CSV/PDF of Dashboard Metrics

[codeZe-us]

Create a backend API route that generates a downloadable CSV or PDF report summarizing the dashboard's financial metrics over a requested date range.

Contribution Guide

• PRs go to the dev branch, not main
• Please application must explain a short specific approach to this task
• PR description must clearly describe what you built and changed
• Link your PR to the correct issue number

Implementation Guidelines

• Key files: src/app/api/v1/dashboard/export/route.ts, src/server/utils/export.utils.ts
• Create a GET method accepting ?format=csv (or pdf) and date range parameters.
• Aggregate the metrics from the DB and use a library like json2csv or pdfmake to generate the file buffer.
• Set proper Content-Disposition headers to trigger a file download in the browser.

Expectations

• What done looks like: Hitting the endpoint initiates an immediate file download in the browser containing accurate financial summaries for the specified dates.
• Discord for questions: codeze_us

[raymondjoseph02]

@raymondjoseph02 has applied to work on this issue as part of the Stellar Wave Program's 5th wave.

Hi maintainers,

I’d like to work on issue #475: “[FEATURE] Generate CSV/PDF of Dashboard Metrics.”

My approach is to create a new GET export endpoint in src/app/api/v1/dashboard/export/route.ts that accepts format, startDate, and endDate query parameters. I’ll aggregate the required dashboard financial metrics from the database, then move the export generation logic into src/server/utils/export.utils.ts for cleaner separation and reusability.

For CSV generation, I plan to use json2csv, and for PDF generation, I’ll use pdfmake to structure the financial summaries clearly. I’ll also configure proper Content-Disposition and content-type headers so the browser immediately downloads the generated report file.

The implementation will include:

• Date range validation
• Accurate financial aggregation
• CSV and PDF buffer generation
• Download-ready API responses
• Clean utility abstraction for future export extensions

I’ll keep the PR focused on this feature and target the dev branch as requested.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @raymondjoseph02 to this issue.

[drips-wave]

Congratulations, @raymondjoseph02! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 2, 2026.

🧑‍💻 @raymondjoseph02: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊