Skip to content

Dashboard: Various Asset page updates #7212

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

Merged
merged 1 commit into from
May 29, 2025

Conversation

MananTank
Copy link
Member

@MananTank MananTank commented May 29, 2025


PR-Codex overview

This PR focuses on enhancing tracking functionality by refactoring tracking parameters and improving error handling in various components. It also simplifies the display of UI elements and adjusts the logic for handling timestamps.

Detailed summary

  • Changed label for Engine in ProjectSidebarLayout.tsx to a string.
  • Improved timestamp formatting in RecentTransfers.tsx.
  • Refactored launchTracking function to accept a more structured params object in launch-token.tsx.
  • Updated tracking calls in CreateTokenAssetPage for better error handling.
  • Enhanced tracking data structure in tracking.ts.
  • Added a trackAssetBuy function to handle buy tracking in ClaimTokenCardUI.tsx.
  • Implemented success and error screens in ClaimTokenCardUI.tsx for purchase confirmation.
  • Adjusted price display logic in ClaimTokenCardUI.tsx to show "FREE" for zero prices.

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

Summary by CodeRabbit

  • New Features

    • Added a success screen after purchasing tokens, displaying confirmation details and options to view the transaction or buy more.
    • Enhanced analytics tracking for token purchase and deployment flows, capturing more detailed error information and contextual metadata.
  • Bug Fixes

    • Improved timestamp handling for recent transfers to ensure consistent display of relative times.
  • Style

    • Updated the sidebar to remove the "New" badge from the "Engine" link.
  • Refactor

    • Streamlined analytics tracking functions to use structured parameter objects and improved error message handling.
  • Chores

    • Minor cleanup, including removal of unnecessary console logs.

Copy link

vercel bot commented May 29, 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 May 29, 2025 11:51pm
4 Skipped Deployments
Name Status Preview Comments Updated (UTC)
docs-v2 ⬜️ Skipped (Inspect) May 29, 2025 11:51pm
login ⬜️ Skipped (Inspect) May 29, 2025 11:51pm
thirdweb_playground ⬜️ Skipped (Inspect) May 29, 2025 11:51pm
wallet-ui ⬜️ Skipped (Inspect) May 29, 2025 11:51pm

@vercel vercel bot temporarily deployed to Preview – wallet-ui May 29, 2025 23:00 Inactive
@vercel vercel bot temporarily deployed to Preview – thirdweb_playground May 29, 2025 23:00 Inactive
@vercel vercel bot temporarily deployed to Preview – docs-v2 May 29, 2025 23:00 Inactive
@vercel vercel bot temporarily deployed to Preview – login May 29, 2025 23:00 Inactive
Copy link
Contributor

coderabbitai bot commented May 29, 2025

Walkthrough

The changes introduce structured analytics tracking for token-related actions, refactor tracking utility functions to accept parameter objects with error message support, and enhance error reporting in tracking events. UI improvements include a new success screen for token claims, improved price display, and removal of a "New" badge from the Engine sidebar link. Date parsing is made more robust for recent transfers.

Changes

File(s) Change Summary
.../erc20/_components/RecentTransfers.tsx Improved block timestamp parsing to ensure UTC interpretation by appending "Z" if missing before creating Date objects.
.../erc20/_components/claim-tokens/claim-tokens-ui.tsx Added analytics tracking for token purchase attempts, successes, and errors, including wallet and error details. Introduced a success screen UI after purchases, improved price display for free tokens, and performed minor code cleanup.
.../assets/create/create-token-page-impl.tsx Refactored tracking calls to use parameter objects instead of positional arguments, now including error messages in error events for deployment, airdrop, mint, and claim-conditions actions.
.../assets/create/launch/launch-token.tsx Refactored the internal launchTracking helper to accept parameter objects with error messages for error events, updating all usages accordingly.
.../assets/create/tracking.ts Refactored tracking utility functions to accept parameter objects (discriminated unions), added explicit error message support in error cases, and updated function signatures accordingly.
.../components/ProjectSidebarLayout.tsx Changed the "Engine" sidebar link label from a JSX element with a "New" badge to a plain string "Engine".

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant ClaimTokenCardUI
    participant Analytics
    participant Blockchain

    User->>ClaimTokenCardUI: Initiate token claim
    ClaimTokenCardUI->>Analytics: trackAssetBuy(type: "attempt", metadata)
    ClaimTokenCardUI->>Blockchain: approveAndClaim()
    alt Approval or Claim fails
        ClaimTokenCardUI->>Analytics: trackAssetBuy(type: "error", errorMessage, metadata)
        ClaimTokenCardUI-->>User: Show error
    else Success
        ClaimTokenCardUI->>Analytics: trackAssetBuy(type: "success", metadata)
        ClaimTokenCardUI-->>User: Show success screen with transaction info
    end
Loading
sequenceDiagram
    participant UI
    participant TrackingUtils

    UI->>TrackingUtils: getTokenDeploymentTrackingData({ type, chainId, errorMessage? })
    TrackingUtils-->>UI: Return tracking data object (includes errorMessage if type is "error")
    UI->>Analytics: Send tracking event with data
Loading

Suggested reviewers

  • joaquim-verges
  • MananTank

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 b1e46d4 and a1aba29.

📒 Files selected for processing (6)
  • apps/dashboard/src/app/(app)/(dashboard)/(chain)/[chain_id]/[contractAddress]/public-pages/erc20/_components/RecentTransfers.tsx (1 hunks)
  • apps/dashboard/src/app/(app)/(dashboard)/(chain)/[chain_id]/[contractAddress]/public-pages/erc20/_components/claim-tokens/claim-tokens-ui.tsx (11 hunks)
  • apps/dashboard/src/app/(app)/team/[team_slug]/[project_slug]/(sidebar)/assets/create/create-token-page-impl.tsx (6 hunks)
  • apps/dashboard/src/app/(app)/team/[team_slug]/[project_slug]/(sidebar)/assets/create/launch/launch-token.tsx (2 hunks)
  • apps/dashboard/src/app/(app)/team/[team_slug]/[project_slug]/(sidebar)/assets/create/tracking.ts (2 hunks)
  • apps/dashboard/src/app/(app)/team/[team_slug]/[project_slug]/(sidebar)/components/ProjectSidebarLayout.tsx (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (6)
  • apps/dashboard/src/app/(app)/team/[team_slug]/[project_slug]/(sidebar)/components/ProjectSidebarLayout.tsx
  • apps/dashboard/src/app/(app)/(dashboard)/(chain)/[chain_id]/[contractAddress]/public-pages/erc20/_components/RecentTransfers.tsx
  • apps/dashboard/src/app/(app)/team/[team_slug]/[project_slug]/(sidebar)/assets/create/launch/launch-token.tsx
  • apps/dashboard/src/app/(app)/team/[team_slug]/[project_slug]/(sidebar)/assets/create/create-token-page-impl.tsx
  • apps/dashboard/src/app/(app)/(dashboard)/(chain)/[chain_id]/[contractAddress]/public-pages/erc20/_components/claim-tokens/claim-tokens-ui.tsx
  • apps/dashboard/src/app/(app)/team/[team_slug]/[project_slug]/(sidebar)/assets/create/tracking.ts
⏰ Context from checks skipped due to timeout of 90000ms (8)
  • GitHub Check: Size
  • GitHub Check: E2E Tests (pnpm, esbuild)
  • GitHub Check: Build Packages
  • GitHub Check: E2E Tests (pnpm, webpack)
  • GitHub Check: Lint Packages
  • GitHub Check: E2E Tests (pnpm, vite)
  • GitHub Check: Unit Tests
  • 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 May 29, 2025 23:00
@MananTank MananTank requested review from a team as code owners May 29, 2025 23:00
@github-actions github-actions bot added the Dashboard Involves changes to the Dashboard. label May 29, 2025
Copy link
Member Author

MananTank commented May 29, 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

codecov bot commented May 29, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 55.63%. Comparing base (deeca88) to head (a1aba29).
Report is 1 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #7212   +/-   ##
=======================================
  Coverage   55.63%   55.63%           
=======================================
  Files         908      908           
  Lines       58546    58546           
  Branches     4128     4128           
=======================================
  Hits        32572    32572           
  Misses      25868    25868           
  Partials      106      106           
Flag Coverage Δ
packages 55.63% <ø> (ø)
🚀 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.

@graphite-app graphite-app bot changed the base branch from 05-28-_tool-4621_new_erc20_public_contract_page to graphite-base/7212 May 29, 2025 23:03
Copy link
Contributor

github-actions bot commented May 29, 2025

size-limit report 📦

Path Size Loading time (3g) Running time (snapdragon) Total time
thirdweb (esm) 62.11 KB (0%) 1.3 s (0%) 163 ms (+100.65% 🔺) 1.5 s
thirdweb (cjs) 345.28 KB (0%) 7 s (0%) 628 ms (+5.31% 🔺) 7.6 s
thirdweb (minimal + tree-shaking) 5.7 KB (0%) 114 ms (0%) 57 ms (+693.12% 🔺) 170 ms
thirdweb/chains (tree-shaking) 531 B (0%) 11 ms (0%) 14 ms (+617.32% 🔺) 24 ms
thirdweb/react (minimal + tree-shaking) 19.52 KB (0%) 391 ms (0%) 59 ms (+429.11% 🔺) 449 ms

Copy link
Contributor

graphite-app bot commented May 29, 2025

Merge activity

@graphite-app graphite-app bot changed the base branch from graphite-base/7212 to main May 29, 2025 23:12
@MananTank MananTank force-pushed the 05-30-dashboard_various_asset_page_updates branch from 8d5a160 to 28ab053 Compare May 29, 2025 23:20
Copy link

changeset-bot bot commented May 29, 2025

⚠️ No Changeset found

Latest commit: a1aba29

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

@vercel vercel bot temporarily deployed to Preview – login May 29, 2025 23:20 Inactive
@vercel vercel bot temporarily deployed to Preview – wallet-ui May 29, 2025 23:20 Inactive
@vercel vercel bot temporarily deployed to Preview – thirdweb_playground May 29, 2025 23:20 Inactive
@vercel vercel bot temporarily deployed to Preview – docs-v2 May 29, 2025 23:20 Inactive
@MananTank MananTank force-pushed the 05-30-dashboard_various_asset_page_updates branch from 28ab053 to b1e46d4 Compare May 29, 2025 23:20
@vercel vercel bot temporarily deployed to Preview – docs-v2 May 29, 2025 23:20 Inactive
@vercel vercel bot temporarily deployed to Preview – wallet-ui May 29, 2025 23:20 Inactive
@vercel vercel bot temporarily deployed to Preview – login May 29, 2025 23:20 Inactive
@vercel vercel bot temporarily deployed to Preview – thirdweb_playground May 29, 2025 23:20 Inactive
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: 1

🧹 Nitpick comments (1)
apps/dashboard/src/app/(app)/team/[team_slug]/[project_slug]/(sidebar)/assets/create/tracking.ts (1)

26-52: Note: Discriminated union property naming inconsistency.

The function implementation is correct and properly handles error message inclusion. However, there's a naming inconsistency where this function uses status for the discriminated union property, while getTokenDeploymentTrackingData and getLaunchTrackingData use type. Consider standardizing the property name across all functions for better developer experience.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 3b1e16c and b1e46d4.

📒 Files selected for processing (6)
  • apps/dashboard/src/app/(app)/(dashboard)/(chain)/[chain_id]/[contractAddress]/public-pages/erc20/_components/RecentTransfers.tsx (1 hunks)
  • apps/dashboard/src/app/(app)/(dashboard)/(chain)/[chain_id]/[contractAddress]/public-pages/erc20/_components/claim-tokens/claim-tokens-ui.tsx (11 hunks)
  • apps/dashboard/src/app/(app)/team/[team_slug]/[project_slug]/(sidebar)/assets/create/create-token-page-impl.tsx (6 hunks)
  • apps/dashboard/src/app/(app)/team/[team_slug]/[project_slug]/(sidebar)/assets/create/launch/launch-token.tsx (2 hunks)
  • apps/dashboard/src/app/(app)/team/[team_slug]/[project_slug]/(sidebar)/assets/create/tracking.ts (2 hunks)
  • apps/dashboard/src/app/(app)/team/[team_slug]/[project_slug]/(sidebar)/components/ProjectSidebarLayout.tsx (1 hunks)
🧰 Additional context used
🧬 Code Graph Analysis (2)
apps/dashboard/src/app/(app)/team/[team_slug]/[project_slug]/(sidebar)/assets/create/create-token-page-impl.tsx (1)
apps/dashboard/src/app/(app)/team/[team_slug]/[project_slug]/(sidebar)/assets/create/tracking.ts (1)
  • getTokenDeploymentTrackingData (1-23)
apps/dashboard/src/app/(app)/team/[team_slug]/[project_slug]/(sidebar)/assets/create/launch/launch-token.tsx (1)
apps/dashboard/src/app/(app)/team/[team_slug]/[project_slug]/(sidebar)/assets/create/tracking.ts (1)
  • getLaunchTrackingData (55-84)
⏰ 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: E2E Tests (pnpm, vite)
  • GitHub Check: Build Packages
  • GitHub Check: Unit Tests
  • GitHub Check: Lint Packages
  • GitHub Check: Analyze (javascript)
🔇 Additional comments (16)
apps/dashboard/src/app/(app)/(dashboard)/(chain)/[chain_id]/[contractAddress]/public-pages/erc20/_components/RecentTransfers.tsx (1)

110-119: LGTM! Excellent defensive programming for timestamp handling.

This change ensures consistent UTC timezone interpretation for blockchain timestamps, preventing potential timezone-related display issues in the relative time formatting. The conditional logic properly handles both timestamped strings with and without the "Z" suffix.

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

78-78: LGTM: Clean UI simplification

Removing the "New" badge from the Engine link simplifies the sidebar interface. The change maintains all functionality while cleaning up the UI.

apps/dashboard/src/app/(app)/(dashboard)/(chain)/[chain_id]/[contractAddress]/public-pages/erc20/_components/claim-tokens/claim-tokens-ui.tsx (7)

3-4: LGTM: Well-organized imports for new functionality

The additional imports support the new tracking, success screen, and enhanced UI features being introduced.

Also applies to: 10-10, 13-13, 29-33


58-58: LGTM: Clean state management for success flow

The activeWallet hook enables wallet ID tracking, and the successScreen state properly manages the post-purchase UI with transaction hash capture.

Also applies to: 66-71


73-97: LGTM: Well-structured analytics tracking function

The trackAssetBuy function correctly implements the discriminated union pattern for tracking events with proper error message handling. The inclusion of contextual metadata (wallet ID, chain ID, account address) provides valuable analytics data.


114-116: LGTM: Comprehensive tracking throughout the purchase flow

Excellent tracking implementation that captures all key events:

  • Attempt tracking before starting the process
  • Error tracking with detailed error messages on both approval and claim failures
  • Success tracking with transition to success screen

This provides complete visibility into the purchase funnel.

Also applies to: 151-154, 186-189, 203-209


171-171: LGTM: Proper transaction receipt handling

Returning the awaited receipt enables the success screen to capture the transaction hash for display and blockchain explorer linking.


259-302: LGTM: Excellent success screen implementation

The success screen provides clear confirmation with:

  • Visual success indicator
  • Purchase details (quantity and token symbol)
  • Transaction link to blockchain explorer
  • "Buy More" option to reset the flow

This significantly improves the user experience after a successful purchase.


337-343: LGTM: Enhanced price display logic

The "FREE" display for zero-price tokens improves clarity for users. The logic correctly handles both per-token and total price calculations with proper conditional rendering.

Also applies to: 365-374

apps/dashboard/src/app/(app)/team/[team_slug]/[project_slug]/(sidebar)/assets/create/create-token-page-impl.tsx (3)

65-68: LGTM: Consistent tracking API refactoring

The refactoring from individual parameters to a parameter object with the type and chainId properties aligns with the new tracking API structure defined in tracking.ts.

Also applies to: 115-118


142-143: LGTM: Enhanced error tracking with explicit messages

Excellent improvement in error tracking by:

  • Extracting error messages from caught exceptions when they are Error instances
  • Providing "Unknown error" fallback for non-Error exceptions
  • Including error messages in tracking data for better debugging

This enhancement significantly improves the quality of analytics data for troubleshooting failed operations.

Also applies to: 150-151, 215-216, 285-286, 384-385


147-152: LGTM: Proper error tracking with structured parameters

The deployment error tracking correctly uses the new parameter object format with type: "error", chainId, and errorMessage properties, maintaining consistency with the refactored tracking API.

apps/dashboard/src/app/(app)/team/[team_slug]/[project_slug]/(sidebar)/assets/create/launch/launch-token.tsx (3)

49-67: LGTM: Well-structured tracking function refactoring

The launchTracking function correctly implements the discriminated union pattern with:

  • type: "attempt" | "success" for basic events
  • type: "error" with required errorMessage for error events
  • Proper parameter spreading to getLaunchTrackingData

This maintains type safety while enabling enhanced error reporting.


69-71: LGTM: Consistent tracking call updates

The calls to launchTracking correctly use the new object parameter format for attempt and success events, maintaining consistency with the refactored API.

Also applies to: 98-100


105-109: LGTM: Enhanced error tracking with message extraction

The error tracking properly:

  • Uses the type: "error" discriminated union
  • Extracts error messages from Error instances
  • Provides "Unknown error" fallback for non-Error exceptions

This improvement enables better debugging and error analysis in the analytics data.

apps/dashboard/src/app/(app)/team/[team_slug]/[project_slug]/(sidebar)/assets/create/tracking.ts (1)

55-84: LGTM! Well-implemented discriminated union with proper error handling.

The function correctly implements discriminated union types and properly includes error messages in tracking data when errors occur. The type safety and conditional error message handling are well-structured.

<!--

## 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 tracking functionality and improving the UI components for better user feedback during token operations in the dashboard application.

### Detailed summary
- Updated `ProjectSidebarLayout.tsx` to simplify the `label` for the Engine section.
- Refactored date formatting in `RecentTransfers.tsx` for improved readability.
- Enhanced error handling and tracking in `launch-token.tsx`, `create-token-page-impl.tsx`, and `tracking.ts`.
- Improved tracking data structure by consolidating parameters in functions.
- Added success and error tracking in `ClaimTokenCardUI` for better user feedback during transactions.

> ✨ 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**
  - Added a success screen after purchasing tokens, displaying confirmation details and options to view the transaction or buy more.
  - Enhanced analytics tracking for token purchase and deployment flows, capturing more detailed error information and contextual metadata.

- **Bug Fixes**
  - Improved timestamp handling for recent transfers to ensure consistent display of relative times.

- **Style**
  - Updated the sidebar to remove the "New" badge from the "Engine" link.

- **Refactor**
  - Streamlined analytics tracking functions to use structured parameter objects and improved error message handling.

- **Chores**
  - Minor cleanup, including removal of unnecessary console logs.

<!-- end of auto-generated comment: release notes by coderabbit.ai -->
@graphite-app graphite-app bot force-pushed the 05-30-dashboard_various_asset_page_updates branch from b1e46d4 to a1aba29 Compare May 29, 2025 23:43
@vercel vercel bot temporarily deployed to Preview – login May 29, 2025 23:43 Inactive
@vercel vercel bot temporarily deployed to Preview – docs-v2 May 29, 2025 23:43 Inactive
@vercel vercel bot temporarily deployed to Preview – thirdweb_playground May 29, 2025 23:43 Inactive
@vercel vercel bot temporarily deployed to Preview – wallet-ui May 29, 2025 23:43 Inactive
@graphite-app graphite-app bot merged commit a1aba29 into main May 29, 2025
24 checks passed
@graphite-app graphite-app bot deleted the 05-30-dashboard_various_asset_page_updates branch May 29, 2025 23:53
@vercel vercel bot temporarily deployed to Production – docs-v2 May 29, 2025 23:53 Inactive
@vercel vercel bot temporarily deployed to Production – login May 29, 2025 23:53 Inactive
@vercel vercel bot temporarily deployed to Production – thirdweb_playground May 29, 2025 23:53 Inactive
@vercel vercel bot temporarily deployed to Production – wallet-ui May 29, 2025 23:53 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