Feat/recently viewed keys 864 - #900
Merged
Chucks1093 merged 7 commits intoSep 6, 2026
Merged
Conversation
Track the last 5 creator keys a user visits on the key detail page in a localStorage-backed store (newest first) and surface them on the homepage for connected users, below the trending leaderboard. - Add useRecentlyViewed persisted store (max 5 entries, newest first) - Record key detail visits in CreatorDetailPage - Render compact RecentlyViewed cards (avatar, name, current price, 24h change) - Add RecentlyViewedSection on the homepage, hidden for guests / empty state - Remove a key from recently viewed when added to the watchlist - Clear the list on wallet disconnect
|
@Seunfunmi-319509 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! 🚀 |
…DetailPage The remote merge removed the useRecentlyViewed call and WatchlistButton JSX from CreatorDetailPage while keeping their imports, causing ESLint no-unused-vars errors on CI. Also adds missing Bookmark icon import in Header.tsx. Closes accesslayerorg#864 🤖 Generated with Codebuff Co-Authored-By: Codebuff <noreply@codebuff.com>
…#900) The last dev merge into feat/recently-viewed-keys-864 carried over dev's own badly-resolved merge (e498adc in accesslayerorg#898), which left several files with duplicate, unparseable content that broke `pnpm lint` and `tsc`: - slippageTolerance.utils.ts / SlippageToleranceSelector.tsx / KeySimulationTool.tsx and their tests were each stitched from two generations of the API (accesslayerorg#872-era and accesslayerorg#877/accesslayerorg#887-era). Restore the implementations the tree's consumers (TradeDialog, LandingPage, CreatorDetailPage) actually use, from the clean pre-merge state. - WatchlistToggle.tsx and its test (dev accesslayerorg#861 artifacts) cannot compile against the wallet-scoped zustand watchlist store used by this branch's components; drop them and restore the store from the branch's own last good state, matching the accesslayerorg#870 resolution. Verified locally: pnpm lint clean, pnpm build green, 46 watchlist / slippage / recently-viewed tests pass. 🤖 Generated with Codebuff Co-Authored-By: Codebuff <noreply@codebuff.com>
Contributor
Author
|
@Chucks1093 all checks passed and all conflicts resolved |
Member
|
Fix Merge conflict |
Member
|
CI is green but this PR has a merge conflict with dev and cannot be auto-merged. Pull the latest dev into your branch with git fetch origin && git checkout your-branch && git merge origin/dev, resolve any conflicts, then run npm run build and npm run lint to confirm everything is clean before pushing. |
Contributor
Author
|
@Chucks1093 all conflicts resolved and checks passed |
Member
|
MERGE CONFLICT |
Contributor
Author
|
@Chucks1093 conflict resolved and checks passed |
Contributor
Author
|
@Chucks1093, please merge Sir, |
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.
PR Summary
Added a Recently Viewed section to the homepage to provide authenticated users with quick access to their last visited keys.
What was done
Acceptance Criteria
Closes #864