Conversation
|
@a1denvalu3 ready for review. i completed all the QA test in the PR description and updated the PR description to reflect the changes. |
| PaymentHistoryEntry( | ||
| id = w.id, | ||
| token = w.token ?: "", | ||
| amount = -w.amountSats, // Negative = outgoing | ||
| date = Date(w.timestamp), | ||
| rawUnit = "sat", | ||
| rawEntryUnit = "sat", | ||
| enteredAmount = w.amountSats, | ||
| bitcoinPrice = null, | ||
| mintUrl = w.mintUrl, | ||
| paymentRequest = w.destination.ifBlank { w.lightningAddress }, | ||
| rawStatus = when (w.status) { | ||
| WithdrawHistoryEntry.STATUS_COMPLETED -> PaymentHistoryEntry.STATUS_COMPLETED | ||
| WithdrawHistoryEntry.STATUS_PENDING -> PaymentHistoryEntry.STATUS_PENDING | ||
| else -> PaymentHistoryEntry.STATUS_COMPLETED | ||
| }, | ||
| paymentType = PaymentHistoryEntry.TYPE_LIGHTNING, | ||
| ) |
There was a problem hiding this comment.
We're converting a withdrawal entry to a PaymentHistoryEntry very loosely. The answer would be to create a History entry that is a union between a payment history entry and a withdrawal history entry.
There was a problem hiding this comment.
i ran your feedback through opus and pushed a fix in this commit: f3a09c8
i also tested the export functionality after building a version with this commit. it works. the csv export looks a bit cleaner: numo_activity_export_2026-03-16 (1).csv
app/src/main/java/com/electricdreams/numo/feature/history/PaymentsHistoryActivity.kt
Show resolved
Hide resolved
|
Conflicts with the main branch |
|
@a1denvalu3 i found a glitch while testing. labels adding to withdrawals are not being saved. i'll work on a fix for this asap. |
|
@a1denvalu3 i fixed the withdrawal label issue (c92e9a9) and pushed a small color update to the delete transaction action (6816279). I think this is ready for review. I also tested the csv export. the labels are all showing for the transactions that have labels. |
The opencode.json config file was accidentally added to the repo. This is a local tool configuration and should not be tracked. Co-Authored-By: Claude Opus 4.6 <[email protected]>
…istoryEntry interface Withdrawals were being shoehorned into PaymentHistoryEntry with fake/empty fields. Now both types implement a shared HistoryEntry interface and are used directly in the history list, CSV export, and transaction detail flows.
6816279 to
4c50f96
Compare
Transaction Details Overhaul
Video Walkthrough
https://drive.proton.me/urls/54ZY89XJ1C#VMHxHhpoSNpT
Summary
Changes
Transaction Details Screen
activity_transaction_detail.xmllayout with cleaner structure and improved typography hierarchy (primary amount large/bold, secondary amount medium, date small)Withdraw Transaction Support
Label Transaction Feature
SharedPreferencesalongside existing payment history dataActivity Screen
PaymentsHistoryAdapterwith multi-view-type support (month headers + transaction items)QA