Skip to content

Dashboard: Fix contract deploy page missing last used teamId in client object #7285

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 5, 2025


PR-Codex overview

This PR focuses on updating the authentication mechanism by replacing the use of getAuthToken with getUserThirdwebClient, streamlining the client initialization process in the PublishedContractPage and DeployFormForUri components.

Detailed summary

  • Replaced getAuthToken with getUserThirdwebClient in page.tsx and uri-based-deploy.tsx.
  • Updated the client initialization logic to remove the dependency on authToken.
  • Adjusted the isLoggedIn prop to always return true in DeployFormForUri.

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

Summary by CodeRabbit

  • Refactor
    • Streamlined user client access, simplifying authentication and client setup in published contract and deploy workflows.
    • Enhanced login state logic for clearer and more efficient user session handling.

Copy link

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

@vercel vercel bot temporarily deployed to Preview – docs-v2 June 5, 2025 13:52 Inactive
@vercel vercel bot temporarily deployed to Preview – wallet-ui June 5, 2025 13:52 Inactive
Copy link

changeset-bot bot commented Jun 5, 2025

⚠️ No Changeset found

Latest commit: 7ab79dc

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 – thirdweb_playground June 5, 2025 13:52 Inactive
@vercel vercel bot temporarily deployed to Preview – login June 5, 2025 13:52 Inactive
@MananTank MananTank marked this pull request as ready for review June 5, 2025 13:52
@MananTank MananTank requested review from a team as code owners June 5, 2025 13:52
Copy link
Contributor

coderabbitai bot commented Jun 5, 2025

Walkthrough

The changes update the authentication and client initialization flow in two dashboard components by replacing the separate fetching of authentication tokens and client creation with a direct call to getUserThirdwebClient. This streamlines the process by obtaining the user client instance directly, removing redundant steps and simplifying the logic.

Changes

Files Change Summary
apps/dashboard/src/app/(app)/(dashboard)/published-contract/[publisher]/[contract_id]/[version]/page.tsx, apps/dashboard/src/app/(app)/(dashboard)/published-contract/components/uri-based-deploy.tsx Replaced separate fetching of auth token and client creation with direct retrieval of user client via getUserThirdwebClient. Removed redundant imports and logic, simplified login checks, and updated component props accordingly.

Suggested labels

Dashboard

Suggested reviewers

  • jnsdls
  • 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 c006cbc and 7ab79dc.

📒 Files selected for processing (2)
  • apps/dashboard/src/app/(app)/(dashboard)/published-contract/[publisher]/[contract_id]/[version]/page.tsx (3 hunks)
  • apps/dashboard/src/app/(app)/(dashboard)/published-contract/components/uri-based-deploy.tsx (3 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • apps/dashboard/src/app/(app)/(dashboard)/published-contract/components/uri-based-deploy.tsx
⏰ Context from checks skipped due to timeout of 90000ms (8)
  • GitHub Check: E2E Tests (pnpm, esbuild)
  • GitHub Check: E2E Tests (pnpm, webpack)
  • GitHub Check: Size
  • GitHub Check: E2E Tests (pnpm, vite)
  • GitHub Check: Build Packages
  • GitHub Check: Unit Tests
  • GitHub Check: Lint Packages
  • GitHub Check: Analyze (javascript)
🔇 Additional comments (3)
apps/dashboard/src/app/(app)/(dashboard)/published-contract/[publisher]/[contract_id]/[version]/page.tsx (3)

11-11: LGTM! Authentication approach simplified.

The import change from getAuthToken to getUserThirdwebClient streamlines the authentication flow by eliminating the need for separate token handling.


96-96: LGTM! Direct client usage improves consistency.

Using the user client directly instead of creating a new client from a JWT token maintains the same functionality while simplifying the code and ensuring consistent client state.


70-75:

✅ Verification successful

Verify the teamId: undefined setting is intentional.

The refactoring eliminates the intermediate auth token step and directly fetches the user client, which simplifies the logic. However, please confirm that setting teamId: undefined is the intended fix for the "missing last used teamId" issue mentioned in the PR objectives.


🏁 Script executed:

#!/bin/bash
# Description: Check how getUserThirdwebClient handles teamId and verify the behavior change
# Expected: Find the implementation and confirm teamId handling

# Search for getUserThirdwebClient implementation
ast-grep --pattern 'function getUserThirdwebClient($$$) {
  $$$
}'

# Also search for getUserThirdwebClient as arrow function or method
rg -A 10 "getUserThirdwebClient.*=.*\(" --type ts --type tsx

Length of output: 1740


Clarify the intentional teamId fallback
Passing teamId: undefined here will make getUserThirdwebClient treat it as “no team ID provided” and automatically fall back to reading the last-used team ID from cookies. If that behavior is exactly what you intend, please add a brief inline comment or JSDoc on this call so future readers understand the implicit fallback.

• File:
apps/dashboard/src/app/(app)/(dashboard)/published-contract/[publisher]/[contract_id]/[version]/page.tsx
Lines ~70–75

Suggested snippet:

// undefined → trigger fallback to last-used teamId in cookies
const [account, client] = await Promise.all([
  getRawAccount(),
  getUserThirdwebClient({ teamId: undefined }),
]);
✨ 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.

Copy link
Member Author


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.

@github-actions github-actions bot added the Dashboard Involves changes to the Dashboard. label Jun 5, 2025
@MananTank MananTank added the hotfix This pull request should be prioritized in the merge queue. label Jun 5, 2025 — with Graphite App
Copy link

codecov bot commented Jun 5, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 55.58%. Comparing base (2b39669) to head (7ab79dc).
Report is 1 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #7285   +/-   ##
=======================================
  Coverage   55.58%   55.58%           
=======================================
  Files         909      909           
  Lines       58670    58670           
  Branches     4158     4158           
=======================================
  Hits        32609    32609           
  Misses      25954    25954           
  Partials      107      107           
Flag Coverage Δ
packages 55.58% <ø> (ø)
🚀 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: 1

♻️ Duplicate comments (1)
apps/dashboard/src/app/(app)/(dashboard)/published-contract/components/uri-based-deploy.tsx (1)

23-28: Same teamId contradiction as previous file.

The concurrent fetching pattern is good, but the same critical issue exists: teamId: undefined contradicts the PR objective of fixing missing last used teamId.

This has the same teamId handling issue as the previous file - please verify the intended teamId behavior.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 2b39669 and c006cbc.

📒 Files selected for processing (2)
  • apps/dashboard/src/app/(app)/(dashboard)/published-contract/[publisher]/[contract_id]/[version]/page.tsx (3 hunks)
  • apps/dashboard/src/app/(app)/(dashboard)/published-contract/components/uri-based-deploy.tsx (3 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (7)
  • 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: Analyze (javascript)
🔇 Additional comments (5)
apps/dashboard/src/app/(app)/(dashboard)/published-contract/[publisher]/[contract_id]/[version]/page.tsx (3)

11-11: Good import update for streamlined client creation.

The import change to use getUserThirdwebClient aligns with the refactoring goal of simplifying the authentication flow.


96-96: Correct addition of client prop.

The client prop is properly passed to the PublishedContract component, completing the refactoring to use the centrally managed client instance.


70-75:

❌ Incorrect review comment

Verify the teamId handling contradicts the PR objective.

The concurrent fetching pattern using Promise.all is excellent for performance. However, there's a critical contradiction: the PR objective states "Fix contract deploy page missing last used teamId in client object" but the implementation explicitly sets teamId: undefined. This suggests either:

  1. The PR description is incorrect, or
  2. The implementation should retrieve and use the actual last used teamId instead of undefined

Please verify the intended behavior by checking if getUserThirdwebClient should receive the actual last used teamId:


🏁 Script executed:

#!/bin/bash
# Description: Check the getUserThirdwebClient function signature and usage patterns
# Expected: Find how teamId should be properly passed

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

# Search for other usages of getUserThirdwebClient with teamId
rg -A 3 -B 3 'getUserThirdwebClient.*teamId'

# Search for last used teamId related code
rg -A 5 -B 5 'lastUsed.*teamId|teamId.*lastUsed'

Length of output: 3403


No changes needed for teamId handling
Passing teamId: undefined into getUserThirdwebClient correctly triggers its built-in fallback to read the last used teamId from cookies, satisfying the “fix missing last used teamId” objective. You can ignore the previous concern about explicitly setting teamId to undefined.

Likely an incorrect or invalid review comment.

apps/dashboard/src/app/(app)/(dashboard)/published-contract/components/uri-based-deploy.tsx (2)

6-6: Consistent import change across components.

The import update maintains consistency with the authentication flow refactoring across the published contract feature.


30-32:

✅ Verification successful

Verify the simplified authentication check is sufficient.

The condition now only checks for teams existence instead of authentication tokens. Ensure that getUserThirdwebClient provides adequate authentication validation when teams is null.


🏁 Script executed:

#!/bin/bash
# Description: Verify getUserThirdwebClient behavior when user is not authenticated
# Expected: Find how authentication is handled in getUserThirdwebClient

# Search for getUserThirdwebClient implementation
ast-grep --pattern 'export function getUserThirdwebClient($$$) { $$$ }'

# Search for authentication checks in getUserThirdwebClient
rg -A 10 -B 5 'getUserThirdwebClient.*auth|auth.*getUserThirdwebClient'

Length of output: 1728


🏁 Script executed:

#!/bin/bash
# Locate and display the getAuthToken implementation for review
FILE="$(find apps/dashboard/src/app -type f -name getAuthToken.ts)"
echo "Inspecting: $FILE"
sed -n '1,200p' "$FILE"

Length of output: 1693


🏁 Script executed:

#!/bin/bash
# Find and display the getClientThirdwebClient implementation
FILE_PATH=$(rg -l "export function getClientThirdwebClient" -g '*.ts' | head -n1)
echo "Inspecting: $FILE_PATH"
sed -n '1,200p' "$FILE_PATH"

Length of output: 683


🏁 Script executed:

#!/bin/bash
# Locate and display getConfiguredThirdwebClient implementation
FILE_PATH=$(rg -l "export function getConfiguredThirdwebClient" -g '*.ts' | head -n1)
echo "Inspecting: $FILE_PATH"
sed -n '1,200p' "$FILE_PATH"

Length of output: 3040


🏁 Script executed:

#!/bin/bash
# Display the URI-based deploy component to inspect how `teams` is fetched and used
sed -n '1,200p' 'apps/dashboard/src/app/(app)/(dashboard)/published-contract/components/uri-based-deploy.tsx'

Length of output: 1988


🏁 Script executed:

#!/bin/bash
# Locate and display the getTeams implementation
FILE_PATH=$(rg -l "export async function getTeams" -g '*.ts' | head -n1)
echo "Inspecting: $FILE_PATH"
sed -n '1,200p' "$FILE_PATH"

Length of output: 2602


Authentication via getTeams() already enforces login

The getTeams() call returns null when there’s no valid auth token, which immediately triggers loginRedirect(pathname). This covers both missing and invalid tokens, so no additional checks are needed before using the Thirdweb client.

Copy link
Contributor

github-actions bot commented Jun 5, 2025

size-limit report 📦

Path Size Loading time (3g) Running time (snapdragon) Total time
thirdweb (esm) 62.57 KB (0%) 1.3 s (0%) 195 ms (+152.17% 🔺) 1.5 s
thirdweb (cjs) 345.55 KB (0%) 7 s (0%) 669 ms (+11.48% 🔺) 7.6 s
thirdweb (minimal + tree-shaking) 5.7 KB (0%) 114 ms (0%) 66 ms (+1352.96% 🔺) 180 ms
thirdweb/chains (tree-shaking) 531 B (0%) 11 ms (0%) 28 ms (+1597.49% 🔺) 38 ms
thirdweb/react (minimal + tree-shaking) 19.56 KB (0%) 392 ms (0%) 120 ms (+631.95% 🔺) 511 ms

Copy link
Contributor

graphite-app bot commented Jun 5, 2025

Merge activity

…t object (#7285)

<!--

## 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 updating the authentication mechanism by replacing the usage of `getAuthToken` with `getUserThirdwebClient` in the `page.tsx` and `uri-based-deploy.tsx` files, enhancing the handling of third-party client connections.

### Detailed summary
- Removed `getAuthToken` and its associated logic in `page.tsx`.
- Introduced `getUserThirdwebClient` to fetch the client in `page.tsx`.
- Updated the `isLoggedIn` prop in `PublishedContract` to use `!!account`.
- Adjusted the logic in `uri-based-deploy.tsx` to fetch client and teams without `authToken`.
- Changed the `isLoggedIn` prop to always be `true` in `uri-based-deploy.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

- **Refactor**
  - Streamlined the process for obtaining the user client, simplifying authentication and client initialization for published contract and deploy flows.
  - Improved logic for login checks and client handling, reducing redundant token fetching and making the login state determination more straightforward.

<!-- end of auto-generated comment: release notes by coderabbit.ai -->
@graphite-app graphite-app bot force-pushed the 06-05-dashboard_fix_contract_deploy_page_missing_last_used_teamid_in_client_object branch from c006cbc to 7ab79dc Compare June 5, 2025 14:07
@vercel vercel bot temporarily deployed to Preview – login June 5, 2025 14:07 Inactive
@vercel vercel bot temporarily deployed to Preview – thirdweb_playground June 5, 2025 14:07 Inactive
@vercel vercel bot temporarily deployed to Preview – wallet-ui June 5, 2025 14:07 Inactive
@vercel vercel bot temporarily deployed to Preview – docs-v2 June 5, 2025 14:07 Inactive
@graphite-app graphite-app bot merged commit 7ab79dc into main Jun 5, 2025
24 checks passed
@graphite-app graphite-app bot deleted the 06-05-dashboard_fix_contract_deploy_page_missing_last_used_teamid_in_client_object branch June 5, 2025 14:16
@graphite-app graphite-app bot removed the hotfix This pull request should be prioritized in the merge queue. label Jun 5, 2025
@vercel vercel bot temporarily deployed to Production – wallet-ui June 5, 2025 14:16 Inactive
@vercel vercel bot temporarily deployed to Production – docs-v2 June 5, 2025 14:16 Inactive
@vercel vercel bot temporarily deployed to Production – thirdweb_playground June 5, 2025 14:16 Inactive
@vercel vercel bot temporarily deployed to Production – login June 5, 2025 14:16 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