Skip to content

[TOOL-4642] Fix useTxNotifications errors not shown in project contract pages #7259

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 focuses on enhancing error handling in the ContractLayout component by wrapping its content in an ErrorProvider, which allows for better management of error states throughout the component.

Detailed summary

  • Added ErrorProvider to wrap the main layout.
  • Reformatted the JSX structure for better readability.
  • Removed the old SharedContractLayout and its surrounding div from the previous structure.
  • Maintained the existing components: TeamHeaderLoggedIn, SaveLastUsedProject, and AppFooter.

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

Summary by CodeRabbit

  • New Features
    • Improved error handling on the contract page with enhanced error context support.

Copy link

linear bot commented Jun 3, 2025

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 10:58pm
4 Skipped Deployments
Name Status Preview Comments Updated (UTC)
docs-v2 ⬜️ Skipped (Inspect) Jun 3, 2025 10:58pm
login ⬜️ Skipped (Inspect) Jun 3, 2025 10:58pm
thirdweb_playground ⬜️ Skipped (Inspect) Jun 3, 2025 10:58pm
wallet-ui ⬜️ Skipped (Inspect) Jun 3, 2025 10:58pm

Copy link

changeset-bot bot commented Jun 3, 2025

⚠️ No Changeset found

Latest commit: 3d1c321

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 – docs-v2 June 3, 2025 12:36 Inactive
@vercel vercel bot temporarily deployed to Preview – wallet-ui June 3, 2025 12:36 Inactive
@vercel vercel bot temporarily deployed to Preview – thirdweb_playground June 3, 2025 12:36 Inactive
@vercel vercel bot temporarily deployed to Preview – login June 3, 2025 12:36 Inactive
Copy link
Contributor

coderabbitai bot commented Jun 3, 2025

"""

Walkthrough

The layout component for contract pages now wraps its entire content within an ErrorProvider context. This change ensures that error handling, such as displaying toast errors, is available throughout the contract-related pages. No other modifications to logic, data fetching, or component interfaces were made.

Changes

File(s) Change Summary
apps/dashboard/src/app/(app)/team/[team_slug]/[project_slug]/contract/[chainIdOrSlug]/[contractAddress]/layout.tsx Wrapped all returned JSX in an ErrorProvider context.

Assessment against linked issues

Objective Addressed Explanation
Fix toast errors not shown in contract pages in /team/project (TOOL-4642)

Assessment against linked issues: Out-of-scope changes

No out-of-scope changes found.
"""

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 35cfd61 and 3d1c321.

📒 Files selected for processing (1)
  • apps/dashboard/src/app/(app)/team/[team_slug]/[project_slug]/contract/[chainIdOrSlug]/[contractAddress]/layout.tsx (2 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • apps/dashboard/src/app/(app)/team/[team_slug]/[project_slug]/contract/[chainIdOrSlug]/[contractAddress]/layout.tsx
⏰ 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: E2E Tests (pnpm, vite)
  • GitHub Check: Unit Tests
  • GitHub Check: Build 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 12:37
@MananTank MananTank requested review from a team as code owners June 3, 2025 12:37
@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
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: 0

🧹 Nitpick comments (1)
apps/dashboard/src/app/(app)/team/[team_slug]/[project_slug]/contract/[chainIdOrSlug]/[contractAddress]/layout.tsx (1)

8-8: Simplify the ErrorProvider import path
The deep relative path (../../../../../../../../contexts/error-handler) can be fragile. Consider adding or using an existing TypeScript path alias (e.g. @/contexts/error-handler) to keep imports concise and maintainable.

📜 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 35cfd61.

📒 Files selected for processing (1)
  • apps/dashboard/src/app/(app)/team/[team_slug]/[project_slug]/contract/[chainIdOrSlug]/[contractAddress]/layout.tsx (2 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (8)
  • GitHub Check: Unit Tests
  • GitHub Check: E2E Tests (pnpm, esbuild)
  • GitHub Check: Build Packages
  • GitHub Check: E2E Tests (pnpm, webpack)
  • GitHub Check: Size
  • GitHub Check: Lint Packages
  • GitHub Check: E2E Tests (pnpm, vite)
  • GitHub Check: Analyze (javascript)
🔇 Additional comments (1)
apps/dashboard/src/app/(app)/team/[team_slug]/[project_slug]/contract/[chainIdOrSlug]/[contractAddress]/layout.tsx (1)

63-90: Wrap layout in ErrorProvider to enable toast error handling
By enclosing your entire layout in <ErrorProvider>, any errors within TeamHeaderLoggedIn, SharedContractLayout, or child components will now propagate to the toast system as intended. This change satisfies the PR objective of displaying toast errors on contract pages.

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 (810ec6e) to head (3d1c321).
Report is 1 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #7259   +/-   ##
=======================================
  Coverage   55.57%   55.57%           
=======================================
  Files         909      909           
  Lines       58681    58681           
  Branches     4167     4167           
=======================================
  Hits        32612    32612           
  Misses      25961    25961           
  Partials      108      108           
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.

@MananTank MananTank changed the title [TOOL-4642] Fix toast errors not shown in project contract pages [TOOL-4642] Fix useTxNotifications errors not shown in project contract pages Jun 3, 2025
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%) 274 ms (+53.39% 🔺) 1.6 s
thirdweb (cjs) 345.38 KB (0%) 7 s (0%) 1.2 s (-0.53% 🔽) 8.2 s
thirdweb (minimal + tree-shaking) 5.7 KB (0%) 114 ms (0%) 81 ms (+870.2% 🔺) 195 ms
thirdweb/chains (tree-shaking) 531 B (0%) 11 ms (0%) 62 ms (+2013.64% 🔺) 73 ms
thirdweb/react (minimal + tree-shaking) 19.56 KB (0%) 392 ms (0%) 117 ms (+421.8% 🔺) 508 ms

Copy link
Contributor

graphite-app bot commented Jun 3, 2025

Merge activity

…ct pages (#7259)

<!--

## 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 adding an `ErrorProvider` wrapper around the layout of the `ContractLayout` component to handle errors more effectively.

### Detailed summary
- Added import for `ErrorProvider`.
- Wrapped the main layout in an `ErrorProvider`.
- Removed the previous layout structure while integrating the `ErrorProvider`.
- Maintained the structure of `TeamHeaderLoggedIn`, `SharedContractLayout`, `SaveLastUsedProject`, and `AppFooter` within the new error handling context.

> ✨ 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**
  - Improved error handling on the contract page with the addition of enhanced error context support.

<!-- end of auto-generated comment: release notes by coderabbit.ai -->
@graphite-app graphite-app bot force-pushed the 06-03-_tool-4642_fix_toast_errors_not_shown_in_project_contract_pages branch from 35cfd61 to 3d1c321 Compare June 3, 2025 22:50
@vercel vercel bot temporarily deployed to Preview – login June 3, 2025 22:51 Inactive
@vercel vercel bot temporarily deployed to Preview – docs-v2 June 3, 2025 22:51 Inactive
@vercel vercel bot temporarily deployed to Preview – thirdweb_playground June 3, 2025 22:51 Inactive
@vercel vercel bot temporarily deployed to Preview – wallet-ui June 3, 2025 22:51 Inactive
@graphite-app graphite-app bot merged commit 3d1c321 into main Jun 3, 2025
24 checks passed
@graphite-app graphite-app bot deleted the 06-03-_tool-4642_fix_toast_errors_not_shown_in_project_contract_pages branch June 3, 2025 22:59
@vercel vercel bot temporarily deployed to Production – thirdweb_playground June 3, 2025 22:59 Inactive
@vercel vercel bot temporarily deployed to Production – docs-v2 June 3, 2025 22:59 Inactive
@vercel vercel bot temporarily deployed to Production – wallet-ui June 3, 2025 22:59 Inactive
@vercel vercel bot temporarily deployed to Production – login June 3, 2025 22:59 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