feat(otel): add prisma operation name to tree view for easier scanning

[ericallam]

[changeset-bot]

⚠️ No Changeset found

Latest commit: b481130

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

[coderabbitai]

Walkthrough

This pull request modifies the enrichCreatableEvents.server.ts utility file to add specialized handling for Prisma client operation events. A new import from "@trigger.dev/core/v3" is added, and the enrichStyle function is extended with a conditional branch that triggers when an event's message equals "prisma:client:operation". When this condition is met and the operation name is a string, the function merges the base style with an accessory codepath displaying the operation name; otherwise, it preserves the base style. No public entity signatures are altered.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~12 minutes

• Context-specific logic: The new conditional branch handles a particular event type and requires understanding how enrichStyle processes different event messages and structures
• Data structure familiarity: Reviewer should verify the shape of props.name and the expected behavior when it is or isn't a string
• Import usage: Confirm the imported symbol from "@trigger.dev/core/v3" is appropriately used and necessary

Pre-merge checks and finishing touches

❌ Failed checks (2 warnings)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The PR description contains only a screenshot with no text content. Required sections like Testing, Changelog, and explanation of changes are completely missing.	Add comprehensive description following the template: include issue reference, testing steps, changelog entry, and optional screenshots. Provide written context explaining the changes.
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	You can run @coderabbitai generate docstrings to improve docstring coverage.

✅ Passed checks (1 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and specifically describes the main change: adding Prisma operation names to the tree view to improve visibility and scanning efficiency.

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch Lane-8

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🧹 Nitpick comments (1)

apps/webapp/app/v3/utils/enrichCreatableEvents.server.ts (1)

27-49: Well-structured Prisma operation handling with proper type safety.

The implementation correctly:

• Identifies Prisma client operation events by message
• Type-guards the operation name before use
• Creates an accessory codepath structure for the tree view
• Falls back gracefully when the name isn't a string

The pattern is consistent with existing style enrichment logic in this file.

Optional consideration: If operationName is an empty string, an empty accessory will be displayed. This is likely acceptable behavior, but you may want to add an additional check like operationName.trim() !== "" if empty accessories should be avoided.

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 83ddf72 and b481130.

📒 Files selected for processing (1)

• apps/webapp/app/v3/utils/enrichCreatableEvents.server.ts (2 hunks)

🧰 Additional context used

🧠 Learnings (1)

📓 Common learnings

Learnt from: nicktrn
Repo: triggerdotdev/trigger.dev PR: 2390
File: internal-packages/run-engine/src/engine/index.ts:466-467
Timestamp: 2025-08-14T10:09:02.528Z
Learning: In the triggerdotdev/trigger.dev codebase, it's acceptable to pass `string | undefined` types directly to Prisma operations (both create and update). The codebase consistently uses this pattern and the team is comfortable with how Prisma handles undefined values.

🧬 Code graph analysis (1)

apps/webapp/app/v3/utils/enrichCreatableEvents.server.ts (2)

packages/core/src/v3/index.ts (1)

• flattenAttributes (46-46)

packages/core/src/v3/utils/flattenAttributes.ts (1)

• flattenAttributes (6-14)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (23)

• GitHub Check: units / internal / 🧪 Unit Tests: Internal (5, 8)
• GitHub Check: units / internal / 🧪 Unit Tests: Internal (6, 8)
• GitHub Check: units / internal / 🧪 Unit Tests: Internal (4, 8)
• GitHub Check: units / internal / 🧪 Unit Tests: Internal (8, 8)
• GitHub Check: units / internal / 🧪 Unit Tests: Internal (7, 8)
• GitHub Check: units / internal / 🧪 Unit Tests: Internal (3, 8)
• GitHub Check: units / webapp / 🧪 Unit Tests: Webapp (6, 8)
• GitHub Check: units / webapp / 🧪 Unit Tests: Webapp (5, 8)
• GitHub Check: units / internal / 🧪 Unit Tests: Internal (1, 8)
• GitHub Check: units / internal / 🧪 Unit Tests: Internal (2, 8)
• GitHub Check: units / webapp / 🧪 Unit Tests: Webapp (8, 8)
• GitHub Check: units / webapp / 🧪 Unit Tests: Webapp (7, 8)
• GitHub Check: units / webapp / 🧪 Unit Tests: Webapp (1, 8)
• GitHub Check: units / webapp / 🧪 Unit Tests: Webapp (3, 8)
• GitHub Check: units / packages / 🧪 Unit Tests: Packages (1, 1)
• GitHub Check: units / webapp / 🧪 Unit Tests: Webapp (4, 8)
• GitHub Check: units / webapp / 🧪 Unit Tests: Webapp (2, 8)
• GitHub Check: e2e / 🧪 CLI v3 tests (windows-latest - pnpm)
• GitHub Check: e2e / 🧪 CLI v3 tests (ubuntu-latest - npm)
• GitHub Check: e2e / 🧪 CLI v3 tests (ubuntu-latest - pnpm)
• GitHub Check: e2e / 🧪 CLI v3 tests (windows-latest - npm)
• GitHub Check: typecheck / typecheck
• GitHub Check: Analyze (javascript-typescript)

[coderabbitai]

⚠️ Potential issue | 🟡 Minor

🧩 Analysis chain

Verify usage of accessoryAttributes import.

The flattenAttributes import is correctly used in the new Prisma operation handling. However, accessoryAttributes doesn't appear to be used in this file. Please verify whether this import is necessary or if it can be removed.

---

🏁 Script executed:

#!/bin/bash
# Description: Check if accessoryAttributes is used in the enrichCreatableEvents.server.ts file

# Search for usage of accessoryAttributes in the file
rg -n 'accessoryAttributes' apps/webapp/app/v3/utils/enrichCreatableEvents.server.ts

Length of output: 80

---

Remove unused accessoryAttributes import.

The accessoryAttributes is imported on line 1 but never used in this file. Only flattenAttributes is actively used in the new Prisma operation handling code. Remove accessoryAttributes from the import statement:

import { flattenAttributes } from "@trigger.dev/core/v3";

🤖 Prompt for AI Agents

In apps/webapp/app/v3/utils/enrichCreatableEvents.server.ts around line 1, the
import statement includes an unused symbol `accessoryAttributes`; remove it so
only `flattenAttributes` is imported from "@trigger.dev/core/v3". Update the
import to drop `accessoryAttributes` and ensure no other references to it exist
in the file.