Transaction History API and Next.js 15 Build Fixes#253
Merged
Baskarayelu merged 4 commits intoRemitwise-Org:mainfrom Feb 27, 2026
Merged
Transaction History API and Next.js 15 Build Fixes#253Baskarayelu merged 4 commits intoRemitwise-Org:mainfrom
Baskarayelu merged 4 commits intoRemitwise-Org:mainfrom
Conversation
Contributor
|
please resolve the conflicts |
Contributor
|
@Agbeleshe Can you please resolve the conflicts? |
Contributor
Author
|
@Baskarayelu On it |
- Connect transaction history page to /api/v1/remittance/history endpoint - Add real-time transaction status filtering (all, completed, pending, failed) - Implement search functionality for hash, address, and memo - Add pagination with cursor-based loading - Update TransactionHistoryItem to display full transaction hash - Fix TypeScript errors with proper type casting - Add loading states and error handling - Maintain existing UI/UX design patterns Resolves issue Remitwise-Org#167: Transaction History and Status API
- Resolved all merge conflicts from upstream/main - Preserved transaction history implementation - Updated auth, goals, bills, and insurance APIs - Synced package.json and dependencies - Maintained all existing functionality
Contributor
Author
|
conflict resolved @Baskarayelu |
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
2 participants
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.
Pull Request: Transaction History API and Next.js 15 Build Fixes
close: #167
Description
This PR implements the transaction history and status endpoints and resolves several critical build blockers related to the Next.js 15 migration and Stellar SDK updates.
Key Changes
1. Remittance History and Status APIs
Horizon Integration
fetchTransactionHistoryandfetchTransactionStatustolib/remittance/horizon.tsto fetch payment records directly from the Stellar network.New Endpoints
GET /api/remittance/historycursor,limit)GET /api/remittance/status/[txHash]Documentation
docs/remittance-api.md.2. Next.js 15 & CI Readiness Fixes
Async Route Parameters
[id],[txHash]) to accessparamsasynchronously to comply with Next.js 15 breaking changes.Async Headers/Cookies
split/route.tsand other routes to properlyawait cookies()andheaders().Dependency Cleanup
uuidpackage with nativecrypto.randomUUID()to resolve build-time resolution errors.Stellar SDK Compatibility
Horizon.Serverimports.lib/contracts/insurance.tslib/contracts/bill-payments.tsFilename Casing Fix
SixMonthTrendsWidgetthat caused build failures on case-sensitive filesystems.Verification Results
Automated Tests
npm run lint— Passednpx tsc --noEmit— Passed (All 50+ type errors resolved)npm run build— Passed (Production build successful)Manual Verification