From ed47e93f1d8dd60067bde53850385b48ae7520b4 Mon Sep 17 00:00:00 2001 From: MananTank Date: Wed, 24 Sep 2025 19:19:38 +0000 Subject: [PATCH] [BLD-338] Dashboard: Fix NFTs table owner row not showing data (#8120) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- ## PR-Codex overview This PR introduces a temporary change to the `table.tsx` file in the NFTs component of the dashboard. It sets the `useIndexer` property to `false`, indicating a workaround until a future fix is implemented. ### Detailed summary - Added `useIndexer: false` to the settings in `table.tsx`. - Marked the addition as temporary with a comment: `// TEMPORARY, TODO: Remove when this is fixed in insight`. > ✨ Ask PR-Codex anything about this PR by commenting with `/codex {your question}` ## Summary by CodeRabbit * **Bug Fixes** * Improved reliability of NFT lists in the dashboard, reducing intermittent errors and missing items when viewing NFTs for specific contracts. * Ensures more consistent, up-to-date NFT data is displayed during browsing and refreshes. * Enhances stability of data loading in environments with inconsistent indexing, minimizing failed loads and retries. * No visual/UI changes; behavior is more dependable without altering the interface or workflows. --- .../[chain_id]/[contractAddress]/nfts/components/table.tsx | 1 + 1 file changed, 1 insertion(+) diff --git a/apps/dashboard/src/app/(app)/(dashboard)/(chain)/[chain_id]/[contractAddress]/nfts/components/table.tsx b/apps/dashboard/src/app/(app)/(dashboard)/(chain)/[chain_id]/[contractAddress]/nfts/components/table.tsx index 3d9ac0a65a4..efacaf5ac7e 100644 --- a/apps/dashboard/src/app/(app)/(dashboard)/(chain)/[chain_id]/[contractAddress]/nfts/components/table.tsx +++ b/apps/dashboard/src/app/(app)/(dashboard)/(chain)/[chain_id]/[contractAddress]/nfts/components/table.tsx @@ -58,6 +58,7 @@ export function NFTGetAllTable({ includeOwners: true, start: currentPage * pageSize, tokenByIndex, + useIndexer: false, // TEMPORARY, TODO: Remove when this is fixed in insight }, );