fix(docs): update all lifecycle hooks to use the new unified param object

[ericallam]

No description provided.

[changeset-bot]

⚠️ No Changeset found

Latest commit: b429fed

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

The documentation example in docs/guides/examples/sentry-error-tracking.mdx updates the onFailure callback signature from three positional parameters (payload, error, { ctx }) to a single destructured object parameter ({ payload, error, ctx }). The function body continues to call Sentry.captureException(error, { extra: { payload, ctx } }). No other files or logic changes are indicated.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch ea-branch-83

---

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

🪧 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.
  • 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.
• 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 the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

Other keywords and placeholders

• Add @coderabbitai ignore or @coderabbit 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

Status, Documentation and Community

• Visit our Status Page to check the current availability of CodeRabbit.
• 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.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (2)

docs/guides/examples/sentry-error-tracking.mdx (2)

59-66: Optional: add light redaction and use Scope to avoid oversized/PII payloads.

Raw payload/ctx can be large or contain secrets. Consider setting sanitized extras on a Scope.
Example diff within this block:

-  Sentry.captureException(error, {
-    extra: {
-      payload,
-      ctx,
-    },
-  });
+  Sentry.withScope((scope) => {
+    scope.setExtras({
+      // TODO: redact or truncate sensitive/large fields
+      payload, 
+      ctx,
+    });
+    Sentry.captureException(error);
+  });

Sentry supports both passing extra and configuring a Scope. (docs.sentry.io)

---

50-58: Optional: consider v4-style global hooks in init.ts.

In v4 you can register global lifecycle hooks anywhere (e.g., trigger/init.ts). For discoverability, you might move Sentry init there and/or use tasks.onFailure(({ error, payload, ctx }) => ...) as an alternative to config-level hooks.
Reference: v4 global hooks and init.ts. (trigger.dev)

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

💡 Knowledge Base configuration:

• MCP integration is disabled by default for public repositories
• Jira integration is disabled by default for public repositories
• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 9966011 and b429fed.

📒 Files selected for processing (1)

• docs/guides/examples/sentry-error-tracking.mdx (1 hunks)

⏰ 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). (1)

• GitHub Check: Analyze (javascript-typescript)

🔇 Additional comments (1)

docs/guides/examples/sentry-error-tracking.mdx (1)

59-66: v4 hook signature change looks correct; keep as destructured args.

Trigger.dev v4 unifies lifecycle hook params into a single destructured object. Your onFailure: async ({ payload, error, ctx }) => { ... } matches the v4 API. Also, passing extra directly to Sentry.captureException is supported by the JS SDK.
References: v4 upgrade notes (unified lifecycle hook args). (trigger.dev) Sentry docs (allowed context keys incl. extra). (docs.sentry.io)