feat(ui): main app page, result pages, routing, and Next.js config [UI #5 & UI #8]#178
Merged
Tinna23 merged 1 commit intoStellarCommons:mainfrom Mar 24, 2026
Conversation
|
@NteinPrecious 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 the main application layer — the search page, result pages,
and routing architecture. Also covers Next.js configuration for Docker
and environment handling.
UI #5 and UI #8 are combined here as they are tightly coupled —
the app page depends on the config being in place, and both are
needed before any result page can work end to end.
Changes
UI #5 — Main app page with search bar and tab switching
src/app/app/page.tsx— search page at/app, routes to result pages on submitsrc/app/tx/[hash]/page.tsx— fetches and displays transaction by hash from URLsrc/app/account/[address]/page.tsx— fetches and displays account by address from URLsrc/components/AppShell.tsx— shared wrapper with background, header, context providersrc/components/AppShellContext.ts— context definition with stub values for progressive enhancementUI #8 — Next.js configuration and environment handling
next.config.ts— standalone output enabled for Docker compatibility.env.local.example— all required variables documented with commentspackage.json— scripts updated:dev,build,start,lintArchitecture note
AppShelluses a stub context pattern — all shared state fields(
addEntry,isSaved,saveAddressetc.) are no-ops for now.They will be replaced with real implementations as UI #21 (history),
UI #22 (address book), and UI #24 (personal mode) are completed.
The inner component pattern is used on result pages to avoid
hooks-in-callbacks errors:
How to test
cp .env.local.example .env.local # Set API_URL to your running backend npm install npm run devhttp://localhost:3000/app/tx/[hash]and displays result/account/[address]and displays result/appCloses
Closes #153
Closes #154
Closes #155
Closes #156