Skip to content

[TOOL-4645] Dashboard: Improve Project overview page loading performance #7261

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Conversation

MananTank
Copy link
Member

@MananTank MananTank commented Jun 3, 2025


PR-Codex overview

This PR primarily focuses on improving the LoadingChartState component and its usage across various chart components in the dashboard. It enhances the visual presentation by adding CSS classes and refactoring the loading state handling.

Detailed summary

  • Updated LoadingChartState to accept a className prop for styling.
  • Changed fallback for Suspense in Transactions, RpcMethodBarChartCard, and EngineCloudChartCard to use LoadingChartState with custom heights and borders.
  • Added new asynchronous functions (AsyncTotalSponsoredCard, AsyncAuthMethodDistributionCard, AsyncAppHighlightsCard, AsyncWalletDistributionCard) for loading data and rendering respective cards.
  • Refactored the ProjectAnalytics function to utilize the new async components for better data handling and rendering.

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

Summary by CodeRabbit

  • Refactor

    • Improved loading placeholders across analytics cards by simplifying their appearance and updating styling for a more consistent look.
    • Modularized data fetching for analytics cards, allowing each card to load and handle errors independently for a smoother user experience.
  • New Features

    • Loading states for analytics cards now display updated visual styles with borders and adjusted heights.
  • Style

    • Unified and customizable loading chart styles for better visual consistency.

Copy link

linear bot commented Jun 3, 2025

Copy link

changeset-bot bot commented Jun 3, 2025

⚠️ No Changeset found

Latest commit: dfe4cf0

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

Copy link
Contributor

coderabbitai bot commented Jun 3, 2025

Walkthrough

The changes refactor analytics-related dashboard components to improve loading behavior. Data fetching for analytics cards is now handled by individual async components within Suspense boundaries, each with its own loading and error state. The LoadingChartState component is updated to support customizable styling, and Suspense fallbacks are simplified across several components.

Changes

File(s) Change Summary
.../EngineCloudChartCard/index.tsx
.../RpcMethodBarChartCard/index.tsx
.../Transactions/index.tsx
Simplified Suspense fallback UI: removed wrapper div, directly render LoadingChartState with updated height and border styling.
.../team/[team_slug]/[project_slug]/(sidebar)/page.tsx Refactored analytics data loading: replaced monolithic parallel fetch with per-card async components using Suspense and error handling.
.../components/analytics/empty-chart-state.tsx Updated LoadingChartState to accept optional className prop for flexible styling; uses cn utility for class concatenation.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant Page
    participant AsyncCard
    participant DataSource

    User->>Page: Loads analytics page
    Page->>AsyncCard: Render Suspense boundary for each card
    AsyncCard->>DataSource: Fetch data asynchronously
    DataSource-->>AsyncCard: Return data or error
    AsyncCard-->>Page: Render card or error state
    Page-->>User: Display analytics cards (loading states shown until data arrives)
Loading

Assessment against linked issues

Objective Addressed Explanation
Improve loading times and user experience for AA usage analytics page (TOOL-4645)

Suggested reviewers

  • joaquim-verges

Warning

Review ran into problems

🔥 Problems

Errors were encountered while retrieving linked issues.

Errors (1)
  • TEAM-0000: Entity not found: Issue - Could not find referenced Issue.

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 7573dd6 and dfe4cf0.

📒 Files selected for processing (5)
  • apps/dashboard/src/app/(app)/team/[team_slug]/[project_slug]/(sidebar)/components/EngineCloudChartCard/index.tsx (1 hunks)
  • apps/dashboard/src/app/(app)/team/[team_slug]/[project_slug]/(sidebar)/components/RpcMethodBarChartCard/index.tsx (1 hunks)
  • apps/dashboard/src/app/(app)/team/[team_slug]/[project_slug]/(sidebar)/components/Transactions/index.tsx (1 hunks)
  • apps/dashboard/src/app/(app)/team/[team_slug]/[project_slug]/(sidebar)/page.tsx (4 hunks)
  • apps/dashboard/src/components/analytics/empty-chart-state.tsx (2 hunks)
🚧 Files skipped from review as they are similar to previous changes (5)
  • apps/dashboard/src/app/(app)/team/[team_slug]/[project_slug]/(sidebar)/components/RpcMethodBarChartCard/index.tsx
  • apps/dashboard/src/app/(app)/team/[team_slug]/[project_slug]/(sidebar)/components/Transactions/index.tsx
  • apps/dashboard/src/app/(app)/team/[team_slug]/[project_slug]/(sidebar)/components/EngineCloudChartCard/index.tsx
  • apps/dashboard/src/components/analytics/empty-chart-state.tsx
  • apps/dashboard/src/app/(app)/team/[team_slug]/[project_slug]/(sidebar)/page.tsx
⏰ Context from checks skipped due to timeout of 90000ms (7)
  • GitHub Check: E2E Tests (pnpm, esbuild)
  • GitHub Check: E2E Tests (pnpm, webpack)
  • GitHub Check: Unit Tests
  • GitHub Check: Size
  • GitHub Check: E2E Tests (pnpm, vite)
  • GitHub Check: Lint Packages
  • GitHub Check: Analyze (javascript)
✨ Finishing Touches
  • 📝 Generate Docstrings

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@MananTank MananTank marked this pull request as ready for review June 3, 2025 14:49
@MananTank MananTank requested review from a team as code owners June 3, 2025 14:49
@github-actions github-actions bot added the Dashboard Involves changes to the Dashboard. label Jun 3, 2025
Copy link
Member Author

MananTank commented Jun 3, 2025


How to use the Graphite Merge Queue

Add either label to this PR to merge it via the merge queue:

  • merge-queue - adds this PR to the back of the merge queue
  • hotfix - for urgent hot fixes, skip the queue and merge this PR next

You must have a Graphite account in order to use the merge queue. Sign up using this link.

An organization admin has enabled the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

This stack of pull requests is managed by Graphite. Learn more about stacking.

Copy link

vercel bot commented Jun 3, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
thirdweb-www ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jun 3, 2025 4:39pm
4 Skipped Deployments
Name Status Preview Comments Updated (UTC)
docs-v2 ⬜️ Skipped (Inspect) Jun 3, 2025 4:39pm
login ⬜️ Skipped (Inspect) Jun 3, 2025 4:39pm
thirdweb_playground ⬜️ Skipped (Inspect) Jun 3, 2025 4:39pm
wallet-ui ⬜️ Skipped (Inspect) Jun 3, 2025 4:39pm

@vercel vercel bot temporarily deployed to Preview – thirdweb_playground June 3, 2025 14:49 Inactive
@vercel vercel bot temporarily deployed to Preview – wallet-ui June 3, 2025 14:49 Inactive
@vercel vercel bot temporarily deployed to Preview – docs-v2 June 3, 2025 14:49 Inactive
@vercel vercel bot temporarily deployed to Preview – login June 3, 2025 14:49 Inactive
@MananTank MananTank changed the base branch from 06-03-_tool-4651_dashboard_show_error_on_invalid_token_distribution_in_erc20_asset_creation_form to graphite-base/7261 June 3, 2025 14:50
@MananTank MananTank force-pushed the 06-03-_tool-4645_dashboard_improve_project_overview_page_loading_performance branch from a819375 to 7573dd6 Compare June 3, 2025 14:50
@MananTank MananTank force-pushed the graphite-base/7261 branch from 31fbde3 to 6cce31d Compare June 3, 2025 14:50
@MananTank MananTank changed the base branch from graphite-base/7261 to main June 3, 2025 14:50
@vercel vercel bot temporarily deployed to Preview – docs-v2 June 3, 2025 14:50 Inactive
@vercel vercel bot temporarily deployed to Preview – thirdweb_playground June 3, 2025 14:50 Inactive
@vercel vercel bot temporarily deployed to Preview – login June 3, 2025 14:50 Inactive
@vercel vercel bot temporarily deployed to Preview – wallet-ui June 3, 2025 14:50 Inactive
Copy link
Member Author

@coderabbitai review

Copy link
Contributor

coderabbitai bot commented Jun 3, 2025

✅ Actions performed

Review triggered.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

Copy link

codecov bot commented Jun 3, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 55.57%. Comparing base (6cce31d) to head (dfe4cf0).
Report is 1 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #7261   +/-   ##
=======================================
  Coverage   55.57%   55.57%           
=======================================
  Files         909      909           
  Lines       58680    58680           
  Branches     4157     4157           
=======================================
  Hits        32610    32610           
  Misses      25963    25963           
  Partials      107      107           
Flag Coverage Δ
packages 55.57% <ø> (ø)
🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 3

🧹 Nitpick comments (5)
apps/dashboard/src/app/(app)/team/[team_slug]/[project_slug]/(sidebar)/components/RpcMethodBarChartCard/index.tsx (1)

9-10: Consistent refactoring with TODO to address.

The change correctly follows the same pattern as other chart components. However, the TODO comment suggests this loading state implementation may need further improvements.

Consider tracking the TODO comment in a separate issue to ensure the loading state improvements are not forgotten.

apps/dashboard/src/app/(app)/team/[team_slug]/[project_slug]/(sidebar)/components/Transactions/index.tsx (1)

16-16: Good refactoring, but consider height consistency.

The change correctly applies the new LoadingChartState pattern. However, this component uses h-[458px] while other similar components use h-[377px]. Consider whether this height difference is intentional or if standardization would be beneficial.

If the height difference isn't content-specific, consider standardizing the loading state heights across all chart components for better visual consistency.

apps/dashboard/src/app/(app)/team/[team_slug]/[project_slug]/(sidebar)/page.tsx (3)

252-291: Improve error handling consistency and add return type annotation.

The async component implementation is good, but consider these improvements:

  1. The error handling pattern with Promise.allSettled is appropriate for resilience
  2. Missing TypeScript return type annotation
  3. Consider extracting to a separate file for better organization
-async function AsyncTotalSponsoredCard(props: {
+async function AsyncTotalSponsoredCard(props: {
   project: Project;
   range: Range;
   interval: "day" | "week";
   searchParams: PageSearchParams;
-}) {
+}): Promise<JSX.Element> {

Consider moving this and other async components to a separate components/ directory for better file organization.


315-376: Add return type annotation for consistency.

The async component logic is well-implemented with proper error handling using Promise.allSettled. However, it's missing a return type annotation like the other async components should have.

-async function AsyncAppHighlightsCard(props: {
+async function AsyncAppHighlightsCard(props: {
   project: Project;
   range: Range;
   interval: "day" | "week";
   searchParams: PageSearchParams;
   client: ThirdwebClient;
   params: PageParams;
-}) {
+}): Promise<JSX.Element> {

166-173: Consider adding error boundaries around Suspense components.

While the Suspense fallbacks handle loading states well, consider wrapping these components in error boundaries to gracefully handle any runtime errors in the async components.

Example implementation:

<ErrorBoundary fallback={<ErrorStateCard />}>
  <Suspense fallback={<LoadingChartState className="h-[431px] border" />}>
    <AsyncWalletDistributionCard project={project} range={range} />
  </Suspense>
</ErrorBoundary>

This ensures that if an async component throws an error, it doesn't crash the entire page.

Also applies to: 184-192

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 6cce31d and 7573dd6.

📒 Files selected for processing (5)
  • apps/dashboard/src/app/(app)/team/[team_slug]/[project_slug]/(sidebar)/components/EngineCloudChartCard/index.tsx (1 hunks)
  • apps/dashboard/src/app/(app)/team/[team_slug]/[project_slug]/(sidebar)/components/RpcMethodBarChartCard/index.tsx (1 hunks)
  • apps/dashboard/src/app/(app)/team/[team_slug]/[project_slug]/(sidebar)/components/Transactions/index.tsx (1 hunks)
  • apps/dashboard/src/app/(app)/team/[team_slug]/[project_slug]/(sidebar)/page.tsx (4 hunks)
  • apps/dashboard/src/components/analytics/empty-chart-state.tsx (2 hunks)
🧰 Additional context used
🧬 Code Graph Analysis (3)
apps/dashboard/src/app/(app)/team/[team_slug]/[project_slug]/(sidebar)/components/EngineCloudChartCard/index.tsx (1)
apps/dashboard/src/components/analytics/empty-chart-state.tsx (1)
  • LoadingChartState (41-52)
apps/dashboard/src/app/(app)/team/[team_slug]/[project_slug]/(sidebar)/components/RpcMethodBarChartCard/index.tsx (1)
apps/dashboard/src/components/analytics/empty-chart-state.tsx (1)
  • LoadingChartState (41-52)
apps/dashboard/src/app/(app)/team/[team_slug]/[project_slug]/(sidebar)/components/Transactions/index.tsx (1)
apps/dashboard/src/components/analytics/empty-chart-state.tsx (1)
  • LoadingChartState (41-52)
⏰ Context from checks skipped due to timeout of 90000ms (8)
  • GitHub Check: E2E Tests (pnpm, esbuild)
  • GitHub Check: Size
  • GitHub Check: E2E Tests (pnpm, webpack)
  • GitHub Check: Lint Packages
  • GitHub Check: Graphite / mergeability_check
  • GitHub Check: Graphite / mergeability_check
  • GitHub Check: Graphite / mergeability_check
  • GitHub Check: Graphite / mergeability_check
🔇 Additional comments (4)
apps/dashboard/src/app/(app)/team/[team_slug]/[project_slug]/(sidebar)/components/EngineCloudChartCard/index.tsx (1)

9-9: LGTM! Clean refactoring to use the enhanced LoadingChartState.

The change effectively removes the wrapper div and directly applies styling through the new className prop, simplifying the component structure while maintaining the same visual appearance.

apps/dashboard/src/components/analytics/empty-chart-state.tsx (1)

41-52: Excellent enhancement to support flexible styling.

The LoadingChartState component now properly accepts an optional className prop and uses the cn utility to merge default styling with custom classes. This enables the consistent styling approach used across the dashboard components.

The implementation correctly:

  • Maintains backward compatibility with optional className
  • Uses proper TypeScript typing
  • Leverages the cn utility for class merging
  • Preserves the existing loading behavior while adding flexibility
apps/dashboard/src/app/(app)/team/[team_slug]/[project_slug]/(sidebar)/page.tsx (2)

154-163: Good async component pattern with proper error boundaries.

The Suspense wrapper with LoadingChartState fallback provides a consistent loading experience. The async component pattern improves performance by allowing independent loading.


40-40:

✅ Verification successful

Verify LoadingChartState className prop support.

The LoadingChartState component is now being used with a className prop throughout the Suspense fallbacks. Ensure this prop is properly implemented in the component definition.


🏁 Script executed:

#!/bin/bash
# Description: Verify LoadingChartState component supports className prop
# Expected: Component should accept and apply className prop

# Search for LoadingChartState component definition
ast-grep --pattern 'function LoadingChartState($$$) {
  $$$
}'

ast-grep --pattern 'const LoadingChartState = ($$$) => {
  $$$
}'

Length of output: 1203


LoadingChartState supports className prop

Verified that LoadingChartState is defined here:

  • apps/dashboard/src/components/analytics/empty-chart-state.tsx:41–52
    It accepts an optional className?: string and correctly merges it via cn(...). No changes needed.

Copy link
Contributor

graphite-app bot commented Jun 3, 2025

Merge activity

…nce (#7261)

<!--

## title your PR with this format: "[SDK/Dashboard/Portal] Feature/Fix: Concise title for the changes"

If you did not copy the branch name from Linear, paste the issue tag here (format is TEAM-0000):

## Notes for the reviewer

Anything important to call out? Be sure to also clarify these in your comments.

## How to test

Unit tests, playground, etc.

-->

<!-- start pr-codex -->

---

## PR-Codex overview
This PR focuses on improving the loading state of various chart components in the dashboard by enhancing the `LoadingChartState` component with additional styling and refactoring the code to utilize asynchronous components for better performance and user experience.

### Detailed summary
- Updated `LoadingChartState` to accept a `className` prop for custom styling.
- Modified `Suspense` components in `Transactions`, `RpcMethodBarChartCard`, and `EngineCloudChartCard` to use improved `LoadingChartState`.
- Introduced new async components: `AsyncTotalSponsoredCard`, `AsyncAuthMethodDistributionCard`, and `AsyncAppHighlightsCard`.
- Refactored fetching logic for analytics data to use async/await pattern, improving readability and maintainability.

> ✨ Ask PR-Codex anything about this PR by commenting with `/codex {your question}`

<!-- end pr-codex -->

<!-- This is an auto-generated comment: release notes by coderabbit.ai -->

## Summary by CodeRabbit

- **Refactor**
  - Improved loading placeholders across analytics cards by simplifying their appearance and updating styling for a more consistent look.
  - Modularized data fetching for analytics cards, allowing each card to load and handle errors independently for a smoother user experience.

- **New Features**
  - Loading states for analytics cards now display updated visual styles with borders and adjusted heights.

- **Style**
  - Unified and customizable loading chart styles for better visual consistency.

<!-- end of auto-generated comment: release notes by coderabbit.ai -->
@graphite-app graphite-app bot force-pushed the 06-03-_tool-4645_dashboard_improve_project_overview_page_loading_performance branch from 7573dd6 to dfe4cf0 Compare June 3, 2025 16:31
@vercel vercel bot temporarily deployed to Preview – login June 3, 2025 16:31 Inactive
@vercel vercel bot temporarily deployed to Preview – wallet-ui June 3, 2025 16:31 Inactive
@vercel vercel bot temporarily deployed to Preview – thirdweb_playground June 3, 2025 16:31 Inactive
@vercel vercel bot temporarily deployed to Preview – docs-v2 June 3, 2025 16:31 Inactive
Copy link
Contributor

github-actions bot commented Jun 3, 2025

size-limit report 📦

Path Size Loading time (3g) Running time (snapdragon) Total time
thirdweb (esm) 62.57 KB (0%) 1.3 s (0%) 223 ms (+174.79% 🔺) 1.5 s
thirdweb (cjs) 345.62 KB (0%) 7 s (0%) 632 ms (+4.63% 🔺) 7.6 s
thirdweb (minimal + tree-shaking) 5.7 KB (0%) 114 ms (0%) 61 ms (+1282.58% 🔺) 175 ms
thirdweb/chains (tree-shaking) 531 B (0%) 11 ms (0%) 33 ms (+1879.44% 🔺) 44 ms
thirdweb/react (minimal + tree-shaking) 19.56 KB (0%) 392 ms (0%) 91 ms (+334.78% 🔺) 482 ms

@graphite-app graphite-app bot merged commit dfe4cf0 into main Jun 3, 2025
24 checks passed
@graphite-app graphite-app bot deleted the 06-03-_tool-4645_dashboard_improve_project_overview_page_loading_performance branch June 3, 2025 16:40
@vercel vercel bot temporarily deployed to Production – wallet-ui June 3, 2025 16:40 Inactive
@vercel vercel bot temporarily deployed to Production – login June 3, 2025 16:40 Inactive
@vercel vercel bot temporarily deployed to Production – docs-v2 June 3, 2025 16:40 Inactive
@vercel vercel bot temporarily deployed to Production – thirdweb_playground June 3, 2025 16:40 Inactive
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Dashboard Involves changes to the Dashboard.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants