-
Notifications
You must be signed in to change notification settings - Fork 557
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
chore: add dedicatedSupportChannel to TeamResponse #7382
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
🦋 Changeset detectedLatest commit: 99043bc The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
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 |
WalkthroughA new optional field, Changes
Sequence Diagram(s)sequenceDiagram
participant Client
participant ServiceUtils
Client->>ServiceUtils: Request TeamResponse
ServiceUtils-->>Client: Responds with TeamResponse (may include dedicatedSupportChannel)
Warning Review ran into problems🔥 ProblemsErrors were encountered while retrieving linked issues. Errors (1)
📜 Recent review detailsConfiguration used: CodeRabbit UI 📒 Files selected for processing (4)
✅ Files skipped from review due to trivial changes (2)
🚧 Files skipped from review as they are similar to previous changes (2)
⏰ Context from checks skipped due to timeout of 90000ms (8)
✨ Finishing Touches
🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed 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)
Other keywords and placeholders
CodeRabbit Configuration File (
|
How to use the Graphite Merge QueueAdd either label to this PR to merge it via the merge queue:
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. |
There was a problem hiding this 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 newdedicatedSupportChannel
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 benull
. 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 stringProviding these details helps consumers understand the change without inspecting code.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 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)
Codecov ReportAll modified and coverable lines are covered by tests ✅
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
🚀 New features to boost your workflow:
|
4e7aee8
to
99043bc
Compare
size-limit report 📦
|
PR-Codex overview
This PR introduces a new property,
dedicatedSupportChannel
, to theTeamResponse
structure across multiple files, enhancing the data model to include support channel details.Detailed summary
dedicatedSupportChannel
toTeamResponse
inapps/dashboard/src/stories/stubs.ts
.dedicatedSupportChannel
in the mock data inpackages/service-utils/src/mocks.ts
.dedicatedSupportChannel
type definition inpackages/service-utils/src/core/api.ts
.Summary by CodeRabbit