fix: wire pages into router + remove duplicate export + unify Tailwind tokens (#143, #144, #191) - #230
Open
ZacLou wants to merge 2 commits into
Open
Conversation
added 2 commits
August 29, 2026 08:51
…age export Issue Cylo-Traders#143: Most built pages were never wired into the router, and there was no catch-all 404 route. Added routes for /campaigns, /campaigns/new, /dashboard/investor, /dashboard/farmer, /dashboard/admin, and a wildcard * route rendering NotFoundPage. Issue Cylo-Traders#144: Two different components were both named/exported as InvestorDashboardPage — a placeholder in pages/index.tsx and the real implementation in pages/InvestorDashboardPage.tsx. Removed the placeholder and re-exported the real component from pages/index.tsx, matching the pattern already used for other real pages. Closes Cylo-Traders#143, Closes Cylo-Traders#144
…Page onto soil/leaf/status tokens (closes Cylo-Traders#191)
ZacLou
changed the title
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
1 participant
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.
Overview
Closes #143, #144, and #191.
InvestorDashboardPage#144 are tightly coupled — the duplicate export causes the wrong component to be imported when wiring routes, so they are fixed together.CampaignDetailPage,FundCampaignModal, andInvestorDashboardPageto the project's soil/leaf/status design-token system.Issue #191: Unify divergent Tailwind design systems
Problem
CampaignDetailPage,FundCampaignModal, andInvestorDashboardPageused a slate/emerald palette, while the rest of the app (and the newOpenDisputeFormrendered insideCampaignDetailPage) uses the soil/leaf/status token system, causing a visual clash.Fix
Migrated the three components and their direct sub-components (
InvestorSummaryStats,InvestmentCard) to the soil/leaf/status token system:InvestmentCardwithSTATUS_METAfromlib/campaignStatusdark:variants; the app currently uses a single light theme viaindex.cssFiles changed
client/src/pages/CampaignDetailPage.tsxclient/src/components/campaign/FundCampaignModal.tsxclient/src/pages/InvestorDashboardPage.tsxclient/src/components/investor/InvestorSummaryStats.tsxclient/src/components/investor/InvestmentCard.tsxclient/src/pages/index.tsx(re-export change for Two different components are both named/exported asInvestorDashboardPage#144)client/src/App.tsx(route wiring for Most built pages are never wired into the router, and there is no catch-all 404 route #143)Verification
tsc --noEmit --project tsconfig.app.jsonpasses with no errors.