fix(wren-ui): fix multi line chart type to dashbord item type

[andreashimin]

Description

Fix add multi line chart to dashboard cause failed

Summary by CodeRabbit

• New Features
  • Added a new dashboard item type MULTI_LINE to support additional visualization options for dashboards.

[coderabbitai]

Walkthrough

This pull request introduces a new enum value MULTI_LINE to the DashboardItemType enum across two files: the GraphQL client types and server schema. The change expands the available dashboard item types, potentially enabling a new multi-line chart visualization option in the dashboard configuration. The modification is consistent across both the client and server-side type definitions, ensuring type compatibility.

Changes

File	Change Summary
wren-ui/src/apollo/client/graphql/__types__.ts	Added MULTI_LINE enum value to DashboardItemType
wren-ui/src/apollo/server/schema.ts	Added MULTI_LINE enum value to DashboardItemType

Possibly related PRs

• fix(wren-ui): adjust chart properties show correctly #1080: Changes to chart properties that may leverage the new MULTI_LINE enum for multi-line chart visualizations

Suggested reviewers

• fredalai

Poem

🐰 A rabbit's chart of lines so fine,
Hopping through data, design divine!
MULTI_LINE joins the enum's dance,
Bringing graphs a new expanse.
Code leaps forward with graphing glee! 📊

---

📜 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 228cdb8 and a05c327.

📒 Files selected for processing (2)

• wren-ui/src/apollo/client/graphql/__types__.ts (1 hunks)
• wren-ui/src/apollo/server/schema.ts (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (3)

• GitHub Check: Analyze (python)
• GitHub Check: Analyze (javascript-typescript)
• GitHub Check: Analyze (go)

🔇 Additional comments (2)

wren-ui/src/apollo/server/schema.ts (1)

802-802: LGTM! Verify the usage of the new enum value.

The addition of MULTI_LINE to DashboardItemType enum is consistent with other chart types and aligns with the PR objective.

Run the following script to verify the usage of the new enum value:

✅ Verification successful

MULTI_LINE chart type is properly implemented and integrated

The new enum value is correctly defined and all necessary components handle it appropriately. The chart type reuses LineProperties for rendering, which is the expected behavior for a multi-line chart variant.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify the usage of the new MULTI_LINE enum value.

# Test: Search for any existing usage of MULTI_LINE in the codebase.
rg -l "MULTI_LINE"

# Test: Search for any chart type related files that might need updates.
fd -t f -e ts -e tsx "chart|dashboard"

Length of output: 807

---

Script:

#!/bin/bash
# Check implementation in ChartAnswer.tsx and adaptor.ts
rg -A 5 -B 5 "MULTI_LINE" "wren-ui/src/components/pages/home/promptThread/ChartAnswer.tsx" "wren-ui/src/apollo/server/models/adaptor.ts"

# Check if any chart rendering or type handling code needs updates
ast-grep --pattern 'case $_ = "MULTI_LINE"'
ast-grep --pattern 'type === "MULTI_LINE"'

Length of output: 1983

---

Script:

#!/bin/bash
# Check chart rendering implementation
rg -l "renderChart|ChartComponent" "wren-ui/src"
rg -A 10 -B 10 "type.*=.*props" "wren-ui/src/components/pages/home/promptThread/ChartAnswer.tsx"

Length of output: 145

---

Script:

#!/bin/bash
# Find chart-related components and type handling
rg -A 5 "import.*chart" -g "*.tsx" "wren-ui/src"
rg -A 10 "const.*Chart.*=.*" -g "*.tsx" "wren-ui/src"
rg -A 5 "chartType.*=.*" -g "*.tsx" "wren-ui/src"

Length of output: 16290

wren-ui/src/apollo/client/graphql/__types__.ts (1)

181-181: LGTM! The enum value is properly added.

The addition of MULTI_LINE to DashboardItemType enum:

• Maintains alphabetical order
• Is consistent with the server schema

✨ Finishing Touches

• 📝 Generate Docstrings (Beta)

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ 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. (Beta)
• @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.