Files
js/apps/dashboard
MananTank bab4ff5e14 Dashboard: Improved chart responsiveness, code cleanup (#7801)
<!--

## 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 enhancing analytics components by introducing responsive time filters, updating chart components to support new props, and refactoring existing code for improved clarity and functionality.

### Detailed summary
- Removed `range-selector.tsx` and refactored `AnalyticsHeader.tsx`.
- Added `ResponsiveTimeFilters` for better time range handling.
- Updated `EcosystemWalletsSummary` and `EcosystemAnalyticsPage` to use new props.
- Refactored various chart components to accept `selectedChart` and `selectedChartQueryParam`.
- Enhanced `AsyncTransactionsChartCard` and `AsyncTotalSponsoredCard` for better data handling.
- Replaced `LoadingChartState` with responsive loading states across components.
- Consolidated logic for handling time series data in analytics cards.
- Improved type definitions for better clarity and consistency.

> The following files were skipped due to too many changes: `apps/dashboard/src/app/(app)/team/[team_slug]/[project_slug]/(sidebar)/page.tsx`

> ✨ 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

* **New Features**
  * Introduced responsive and modular time filter controls for analytics dashboards.
  * Added new highlights cards for team and project analytics, providing aggregated metrics in a combined bar chart format.
  * Added a new combined bar chart card for gas sponsorship data with dynamic chart selection.
  * Added components that map transaction and sponsorship data with chain metadata for improved analytics detail.

* **Refactor**
  * Replaced multiple analytics and chart components with streamlined, asynchronous, and responsive variants.
  * Standardized date range and interval filtering using a centralized utility and responsive providers.
  * Updated chart selection to use in-app state and callbacks instead of URL-based navigation.
  * Simplified analytics page layouts by replacing Suspense with responsive suspense components.
  * Externalized data processing and state management from several chart card components to improve modularity.
  * Removed deprecated components and replaced them with updated responsive and async implementations.

* **Bug Fixes**
  * Improved handling of date ranges and intervals, ensuring accurate and consistent filtering.

* **Chores**
  * Removed unused or redundant components and consolidated stories for better maintainability.
  * Cleaned up imports and type definitions across analytics and project overview pages.

* **Style**
  * Enhanced button and layout styling for chart selection and analytics cards.

* **Documentation**
  * Updated interactive stories for analytics components to improve clarity and usability.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
2025-08-07 01:24:29 +00:00
..
2025-02-24 22:16:02 -07:00
2025-07-03 18:32:04 -07:00
2025-06-20 16:14:38 -07:00
2025-06-20 16:14:38 -07:00
2025-06-20 16:14:38 -07:00
2025-06-20 16:14:38 -07:00
2025-06-20 16:14:38 -07:00
2025-06-20 16:14:38 -07:00

thirdweb.com

This repo contains the full source for all of thirdweb.com and the thirdweb dashboard.

Starting a local dev server

Run from the root folder (thirdweb-dev/js):

cd <path/to/thirdweb-dev/js>
pnpm dashboard

Building for production

pnpm build

Environment Variables

Some env vars can be overridden that are required for some external services to work. You can find them in the .env.example file at the root level of the project including some descriptions of what they are used for.

To define env vars please create a .env file based on the .env.example template at the root level of the project. This file is ignored by git so you can safely add it to your local copy of the project.

Add your thirdweb clientID and secret key to build a basic functioning version of the site.

Code Structure and Style Guide

Components

  • Components should go in a components folder next to the app page they are used in.
  • If a component is reused in multiple pages, it should go in the lowest level route folder it is used in. For example, if a chart component is used in all analytics subroutes /analytics/..., it should go in the /analytics/components folder.
  • All low-level components such as buttons, inputs, etc. should be shadcn components found in @/ui.
  • All composed components reused across all page routes are blocks, and should also go in the @/ui folder.

Data fetching

  • Use RSC wherever possible.
  • Write data fetching code in its own function in the same file as the component it is used in, not exported.
  • If the same data fetching function is used in multiple components, place it in a file in an api folder at the lowest level possible (just like components). If you need to do this you probable aren't organizing your components properly.