Skip to content

chore: add dedicatedSupportChannel to TeamResponse #7382

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

arcoraven
Copy link
Contributor

@arcoraven arcoraven commented Jun 19, 2025


PR-Codex overview

This PR introduces a new property, dedicatedSupportChannel, to the TeamResponse structure across multiple files, enhancing the data model to include support channel details.

Detailed summary

  • Added dedicatedSupportChannel to TeamResponse in apps/dashboard/src/stories/stubs.ts.
  • Included dedicatedSupportChannel in the mock data in packages/service-utils/src/mocks.ts.
  • Updated dedicatedSupportChannel type definition in packages/service-utils/src/core/api.ts.

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

Summary by CodeRabbit

  • New Features
    • Added a new field to display dedicated support channel information (such as Slack or Telegram) for teams where available.

Copy link

vercel bot commented Jun 19, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
docs-v2 ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jun 19, 2025 1:27pm
login ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jun 19, 2025 1:27pm
nebula ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jun 19, 2025 1:27pm
thirdweb_playground ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jun 19, 2025 1:27pm
thirdweb-www ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jun 19, 2025 1:27pm
wallet-ui ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jun 19, 2025 1:27pm

Copy link

changeset-bot bot commented Jun 19, 2025

🦋 Changeset detected

Latest commit: 99043bc

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
Name Type
@thirdweb-dev/service-utils Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

Copy link
Contributor

coderabbitai bot commented Jun 19, 2025

Walkthrough

A new optional field, dedicatedSupportChannel, has been added to the TeamResponse type in the @thirdweb-dev/service-utils package. This field can be an object specifying a support channel's type and name, or null. No other structural or functional changes were made.

Changes

File(s) Change Summary
.changeset/dry-emus-exist.md Documented the addition of the dedicatedSupportChannel field to TeamResponse.
packages/service-utils/src/core/api.ts, Added optional dedicatedSupportChannel property to the TeamResponse type definition.
packages/service-utils/src/mocks.ts Added dedicatedSupportChannel: null to validTeamResponse mock object.
apps/dashboard/src/stories/stubs.ts Added dedicatedSupportChannel: null to the object returned by teamStub function.

Sequence Diagram(s)

sequenceDiagram
    participant Client
    participant ServiceUtils

    Client->>ServiceUtils: Request TeamResponse
    ServiceUtils-->>Client: Responds with TeamResponse (may include dedicatedSupportChannel)
Loading

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 4e7aee8 and 99043bc.

📒 Files selected for processing (4)
  • .changeset/dry-emus-exist.md (1 hunks)
  • apps/dashboard/src/stories/stubs.ts (1 hunks)
  • packages/service-utils/src/core/api.ts (1 hunks)
  • packages/service-utils/src/mocks.ts (1 hunks)
✅ Files skipped from review due to trivial changes (2)
  • packages/service-utils/src/mocks.ts
  • apps/dashboard/src/stories/stubs.ts
🚧 Files skipped from review as they are similar to previous changes (2)
  • packages/service-utils/src/core/api.ts
  • .changeset/dry-emus-exist.md
⏰ Context from checks skipped due to timeout of 90000ms (8)
  • GitHub Check: Size
  • GitHub Check: E2E Tests (pnpm, esbuild)
  • GitHub Check: E2E Tests (pnpm, vite)
  • GitHub Check: E2E Tests (pnpm, webpack)
  • GitHub Check: Unit Tests
  • GitHub Check: Lint Packages
  • 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.

@arcoraven arcoraven marked this pull request as ready for review June 19, 2025 13:16
@arcoraven arcoraven requested a review from a team as a code owner June 19, 2025 13:16
Copy link
Contributor 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.

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 (2)
packages/service-utils/src/core/api.ts (1)

150-153: Document the new dedicatedSupportChannel field with JSDoc for clarity.

The addition of dedicatedSupportChannel is helpful, but it would be clearer if you add a brief comment explaining its purpose and when it might be null. For example:

/**
 * The team's dedicated support channel (Slack or Telegram). 
 * Null if no channel is configured.
 */
dedicatedSupportChannel: {
  type: "slack" | "telegram";
  name: string;
} | null;

This aligns with existing patterns (e.g., updatedAt: string | null) and improves maintainability for API consumers.

.changeset/dry-emus-exist.md (1)

1-5: Enhance the changeset description for downstream clarity.

The changeset title is concise but could benefit from a short summary of the added field’s structure and usage. For example:

---
"@thirdweb-dev/service-utils": patch
---
Add `dedicatedSupportChannel` to `TeamResponse`

This optional field specifies a team’s support channel:
- `type`: `"slack" | "telegram"`
- `name`: Channel identifier string

Providing these details helps consumers understand the change without inspecting code.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 5492331 and 4e7aee8.

📒 Files selected for processing (2)
  • .changeset/dry-emus-exist.md (1 hunks)
  • packages/service-utils/src/core/api.ts (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (8)
  • GitHub Check: E2E Tests (pnpm, esbuild)
  • GitHub Check: Unit Tests
  • GitHub Check: E2E Tests (pnpm, vite)
  • GitHub Check: Size
  • GitHub Check: Lint Packages
  • GitHub Check: E2E Tests (pnpm, webpack)
  • GitHub Check: Build Packages
  • GitHub Check: Analyze (javascript)

Copy link

codecov bot commented Jun 19, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 52.35%. Comparing base (5492331) to head (99043bc).
Report is 1 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #7382   +/-   ##
=======================================
  Coverage   52.35%   52.35%           
=======================================
  Files         939      939           
  Lines       63161    63161           
  Branches     4217     4217           
=======================================
  Hits        33070    33070           
  Misses      29984    29984           
  Partials      107      107           
Flag Coverage Δ
packages 52.35% <ø> (ø)
🚀 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.

@arcoraven arcoraven force-pushed the ph/06-19-chore_add_dedicatedsupportchannel_to_teamresponse branch from 4e7aee8 to 99043bc Compare June 19, 2025 13:20
@arcoraven arcoraven requested a review from a team as a code owner June 19, 2025 13:20
@github-actions github-actions bot added the Dashboard Involves changes to the Dashboard. label Jun 19, 2025
@arcoraven arcoraven enabled auto-merge (squash) June 19, 2025 13:24
@arcoraven arcoraven disabled auto-merge June 19, 2025 13:24
@arcoraven arcoraven merged commit 4c29886 into main Jun 19, 2025
25 of 26 checks passed
@arcoraven arcoraven deleted the ph/06-19-chore_add_dedicatedsupportchannel_to_teamresponse branch June 19, 2025 13:24
Copy link
Contributor

size-limit report 📦

Path Size Loading time (3g) Running time (snapdragon) Total time
thirdweb (esm) 62.53 KB (0%) 1.3 s (0%) 229 ms (+179.89% 🔺) 1.5 s
thirdweb (cjs) 350.55 KB (0%) 7.1 s (0%) 677 ms (+8.72% 🔺) 7.7 s
thirdweb (minimal + tree-shaking) 5.7 KB (0%) 114 ms (0%) 90 ms (+1796.32% 🔺) 204 ms
thirdweb/chains (tree-shaking) 531 B (0%) 11 ms (0%) 71 ms (+1631.06% 🔺) 82 ms
thirdweb/react (minimal + tree-shaking) 19.59 KB (0%) 392 ms (0%) 105 ms (+753.51% 🔺) 497 ms

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. packages
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant