Getting Started
- Fork the repository: https://github.com/JointSave-org/Joint_Save
- Clone your fork:
git clone https://github.com/<your-username>/Joint_Save.git
cd Joint_Save
- Create a new branch:
git checkout -b improve/transactions-export-consistency
Overview
The Transactions tab already has a CSV export. This issue is about a smaller, focused follow-up: double-check that the exported CSV's date formatting is consistent with the rest of the app now that formatRelativeTime/formatExactDateTime exist, and that the exported amounts correctly reflect each pool's actual token (now that multi-token support has shipped) rather than assuming everything is XLM.
Requirements
- Audit the existing CSV export logic in the Transactions tab
- Confirm amounts in the export are labeled with the correct token symbol per row (not just XLM for everything), now that pools can use different tokens
- Confirm exported dates use a consistent, unambiguous format (full ISO date, not a relative string like "2 hours ago" which wouldn't make sense in an exported file read later)
Acceptance Criteria
Getting Started
Overview
The Transactions tab already has a CSV export. This issue is about a smaller, focused follow-up: double-check that the exported CSV's date formatting is consistent with the rest of the app now that
formatRelativeTime/formatExactDateTimeexist, and that the exported amounts correctly reflect each pool's actual token (now that multi-token support has shipped) rather than assuming everything is XLM.Requirements
Acceptance Criteria