chore: use own DeepResearchEvent

[marcusschiesser]

Summary by CodeRabbit

• New Features
  • Introduced enhanced deep research event tracking within workflows, providing more detailed monitoring of research-related events.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 6e35498

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]

Caution

Review failed

The pull request is closed.

Walkthrough

A new type and class for handling deep research events have been added to the workflow file. The DeepResearchEventData type defines required properties (such as event type, state, id, question, and answer), while the DeepResearchEvent class extends the base workflow event to encapsulate these details under a specific "deep_research_event" label. Additionally, the file’s import statement was updated to now define DeepResearchEvent locally.

Changes

File	Change Summary
templates/.../deep_research/workflow.ts	- Added DeepResearchEventData type with properties: event, state, id, question, answer. - Added DeepResearchEvent class extending WorkflowEvent. - Removed external import for DeepResearchEvent by defining it locally.

Sequence Diagram(s)

sequenceDiagram
    participant Client
    participant Workflow
    participant DeepResearch

    Client->>Workflow: Trigger deep research event
    Workflow->>DeepResearch: Instantiate DeepResearchEvent(data)
    DeepResearch->>Workflow: Process deep research event data
    Workflow-->>Client: Return event handling response

Loading

Poem

I'm a rabbit with a curious mind,
Hopping through the code, treasures to find.
A new event takes a joyful leap,
Deep research secrets, mine to keep.
With each line, I twirl in code delight! 🐇✨

---

📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between e6f8add and 6e35498.

📒 Files selected for processing (1)

• templates/components/workflows/typescript/deep_research/workflow.ts (2 hunks)

✨ Finishing Touches

• 📝 Generate Docstrings

---

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.
  • Generate unit testing code for this file.
  • 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 generate unit testing code for this file.
  • @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 generate unit testing code.
  • @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.

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 resolve resolve all the CodeRabbit review comments.
• @coderabbitai plan to trigger planning for file edits and PR creation.
• @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.

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.