Skip to content

[Dashboard] Add ecosystem name editing functionality #7115

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

Conversation

joaquim-verges
Copy link
Member

@joaquim-verges joaquim-verges commented May 21, 2025


PR-Codex overview

This PR adds functionality for editing the name of an ecosystem in the EcosystemHeader component. It introduces a dialog for name input and updates the ecosystem name upon saving.

Detailed summary

  • Added Input component for name editing.
  • Introduced state variables isNameDialogOpen and tempName.
  • Implemented handleNameSave function for updating the ecosystem name.
  • Added a dialog with a trigger button for editing the name.
  • Updated success message to "Ecosystem updated".

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

Summary by CodeRabbit

  • New Features
    • Added inline editing for the ecosystem name directly from the header, including a dialog with input field and save/cancel options.
  • Bug Fixes
    • Corrected a typo in the tooltip text for copying the ecosystem slug.
  • Improvements
    • Updated success messages to be more general when the ecosystem is updated.

Copy link

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

@vercel vercel bot temporarily deployed to Preview – docs-v2 May 21, 2025 20:21 Inactive
@vercel vercel bot temporarily deployed to Preview – wallet-ui May 21, 2025 20:21 Inactive
@vercel vercel bot temporarily deployed to Preview – login May 21, 2025 20:21 Inactive
Copy link

changeset-bot bot commented May 21, 2025

⚠️ No Changeset found

Latest commit: 27ed2e8

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 May 21, 2025 20:21 Inactive
Copy link

coderabbitai bot commented May 21, 2025

Walkthrough

The update adds inline editing for the ecosystem name within the EcosystemHeader component. It introduces dialog state management, input handling for the new name, an async save handler, and UI changes for editing and saving the name. Minor UI text adjustments and an import for the input component are also included.

Changes

File(s) Change Summary
.../ecosystem-header.client.tsx Added inline name editing: dialog state, temp input, async save handler, dialog UI with input and buttons, input import, typo fix in tooltip, generalized toast message.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant EcosystemHeader
    participant updateEcosystem
    participant Router
    participant Toast

    User->>EcosystemHeader: Click edit (pencil icon)
    EcosystemHeader->>EcosystemHeader: Open name edit dialog
    User->>EcosystemHeader: Change input, click Save
    EcosystemHeader->>EcosystemHeader: Validate and trim name
    alt Name is valid and changed
        EcosystemHeader->>updateEcosystem: Call with new name
        updateEcosystem-->>EcosystemHeader: Success
        EcosystemHeader->>EcosystemHeader: Close dialog
        EcosystemHeader->>Router: Refresh
        EcosystemHeader->>Toast: Show "Ecosystem updated."
    else Name invalid or unchanged
        EcosystemHeader->>EcosystemHeader: Do nothing / Close dialog
    end
    alt Error on update
        EcosystemHeader->>Toast: Show error message
    end
Loading

Note

⚡️ AI Code Reviews for VS Code, Cursor, Windsurf

CodeRabbit now has a plugin for VS Code, Cursor and Windsurf. This brings AI code reviews directly in the code editor. Each commit is reviewed immediately, finding bugs before the PR is raised. Seamless context handoff to your AI code agent ensures that you can easily incorporate review feedback.
Learn more here.


Note

⚡️ Faster reviews with caching

CodeRabbit now supports caching for code and dependencies, helping speed up reviews. This means quicker feedback, reduced wait times, and a smoother review experience overall. Cached data is encrypted and stored securely. This feature will be automatically enabled for all accounts on May 30th. To opt out, configure Review - Disable Cache at either the organization or repository level. If you prefer to disable all data retention across your organization, simply turn off the Data Retention setting under your Organization Settings.
Enjoy the performance boost—your workflow just got faster.

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.
✨ 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 May 21, 2025
Copy link
Contributor

size-limit report 📦

Path Size Loading time (3g) Running time (snapdragon) Total time
thirdweb (esm) 56.57 KB (0%) 1.2 s (0%) 196 ms (+176.06% 🔺) 1.4 s
thirdweb (cjs) 309.52 KB (0%) 6.2 s (0%) 583 ms (+1.49% 🔺) 6.8 s
thirdweb (minimal + tree-shaking) 5.69 KB (0%) 114 ms (0%) 70 ms (+1097.01% 🔺) 184 ms
thirdweb/chains (tree-shaking) 531 B (0%) 11 ms (0%) 14 ms (+621.68% 🔺) 25 ms
thirdweb/react (minimal + tree-shaking) 19.5 KB (0%) 390 ms (0%) 64 ms (+439.31% 🔺) 453 ms

Copy link

codecov bot commented May 21, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 55.60%. Comparing base (72cc27a) to head (27ed2e8).
Report is 1 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #7115   +/-   ##
=======================================
  Coverage   55.60%   55.60%           
=======================================
  Files         901      901           
  Lines       58121    58121           
  Branches     4067     4067           
=======================================
  Hits        32320    32320           
  Misses      25696    25696           
  Partials      105      105           
Flag Coverage Δ
packages 55.60% <ø> (ø)
🚀 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

@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 (2)
apps/dashboard/src/app/(app)/team/[team_slug]/(team)/~/ecosystem/[slug]/(active)/components/ecosystem-header.client.tsx (2)

217-234: Well-implemented save handler with proper validation.

The handleNameSave function includes good validation logic and error handling. It only updates when the name has actually changed and isn't empty.

Consider adding validation for maximum name length to prevent overly long ecosystem names:

  async function handleNameSave() {
    const trimmed = tempName.trim();
-   if (!trimmed || trimmed === ecosystem.name) {
+   if (!trimmed || trimmed === ecosystem.name || trimmed.length > 50) {
      setIsNameDialogOpen(false);
+     if (trimmed.length > 50) {
+       toast.error("Ecosystem name must be 50 characters or less");
+     }
      return;
    }
    // rest of the function...
  }

323-368: Well-structured dialog implementation.

The dialog follows the same pattern as the existing image upload dialog, maintaining UI consistency. The pencil icon button is appropriately placed next to the ecosystem name, and the save button is correctly disabled when the name is empty or during update.

Consider these accessibility improvements:

  <DialogContent className="max-w-[480px]">
    <DialogHeader>
      <DialogTitle>Edit Ecosystem Name</DialogTitle>
    </DialogHeader>

    <div className="flex flex-col gap-4 py-2">
      <Input
        value={tempName}
        onChange={(e) => setTempName(e.target.value)}
+       placeholder="Enter ecosystem name"
+       aria-label="Ecosystem name"
+       maxLength={50}
+       onKeyDown={(e) => {
+         if (e.key === 'Enter' && tempName.trim() && !isUpdating) {
+           handleNameSave();
+         }
+       }}
      />
    </div>
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 72cc27a and 27ed2e8.

📒 Files selected for processing (1)
  • apps/dashboard/src/app/(app)/team/[team_slug]/(team)/~/ecosystem/[slug]/(active)/components/ecosystem-header.client.tsx (6 hunks)
🧰 Additional context used
🧬 Code Graph Analysis (1)
apps/dashboard/src/app/(app)/team/[team_slug]/(team)/~/ecosystem/[slug]/(active)/components/ecosystem-header.client.tsx (2)
apps/dashboard/src/@/components/ui/dialog.tsx (7)
  • Dialog (130-130)
  • DialogTrigger (134-134)
  • DialogContent (135-135)
  • DialogHeader (136-136)
  • DialogTitle (138-138)
  • DialogFooter (137-137)
  • DialogClose (133-133)
apps/dashboard/src/@/components/ui/button.tsx (1)
  • Button (67-67)
🔇 Additional comments (4)
apps/dashboard/src/app/(app)/team/[team_slug]/(team)/~/ecosystem/[slug]/(active)/components/ecosystem-header.client.tsx (4)

26-26: Good addition of the Input component import.

The Input component import is correctly added to support the new name editing functionality.


163-165: Clear state management for name editing.

The state variables are appropriately named and initialized. Using ecosystem.name as the initial value for tempName ensures the input starts with the current name.


178-178: Good generalization of the success message.

Changing the success message to "Ecosystem updated" makes it reusable for both image and name updates.


379-379: Fixed typo in tooltip text.

Corrected "Copy Ecosytem slug" to "Copy Ecosystem slug", improving user experience.

@joaquim-verges joaquim-verges merged commit 77da352 into main May 21, 2025
27 checks passed
@joaquim-verges joaquim-verges deleted the _Dashboard_Add_ecosystem_name_editing_functionality branch May 21, 2025 20:54
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.

1 participant