Skip to content

Conversation

@michelle0927
Copy link
Collaborator

@michelle0927 michelle0927 commented Jul 21, 2025

Resolves #17343

Summary by CodeRabbit

  • New Features

    • Added optional support for specifying a dashboard and enabling collection preview when running a query.
  • Bug Fixes

    • Corrected the URL used for running card queries to ensure accurate API requests.
  • Chores

    • Updated version numbers for several actions and the overall package.
    • Improved action descriptions for clarity.

@vercel
Copy link

vercel bot commented Jul 21, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

3 Skipped Deployments
Name Status Preview Comments Updated (UTC)
docs-v2 ⬜️ Ignored (Inspect) Jul 21, 2025 3:39pm
pipedream-docs ⬜️ Ignored (Inspect) Jul 21, 2025 3:39pm
pipedream-docs-redirect-do-not-edit ⬜️ Ignored (Inspect) Jul 21, 2025 3:39pm

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Jul 21, 2025

Walkthrough

This update increments version numbers for several Metabase action components and the package, corrects the API endpoint used in the runCardQuery method, and enhances the "Run Query" action by adding two optional properties and updating its description URL. No other logic or error handling changes were made.

Changes

File(s) Change Summary
components/metabase/actions/create-dashboard/create-dashboard.mjs Bumped version from 0.0.1 to 0.0.2
components/metabase/actions/get-dashboard/get-dashboard.mjs Bumped version from 0.0.1 to 0.0.2
components/metabase/actions/get-database/get-database.mjs Bumped version from 0.0.1 to 0.0.2
components/metabase/actions/run-query/run-query.mjs Bumped version to 0.0.2; fixed description URL; added optional dashboardId and collectionPreview props; included them in payload
components/metabase/metabase.app.mjs Changed API endpoint in runCardQuery from /card/pivot/${cardId}/query to /card/${cardId}/query
components/metabase/package.json Bumped package version from 0.1.0 to 0.1.1

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant RunQueryAction
    participant MetabaseApp

    User->>RunQueryAction: Trigger Run Query action (with cardId, dashboardId, collectionPreview)
    RunQueryAction->>MetabaseApp: Call runCardQuery({ cardId, dashboard_id, collection_preview })
    MetabaseApp->>Metabase API: POST /card/{cardId}/query with payload
    Metabase API-->>MetabaseApp: Return query results
    MetabaseApp-->>RunQueryAction: Return results
    RunQueryAction-->>User: Output results
Loading

Estimated code review effort

2 (~15 minutes)

Poem

A hop, a skip, a version bump or two,
The endpoint’s fixed—now queries run true!
New props appear, descriptions align,
All in a day’s work—how rabbits refine.
With each little patch, we leap ahead,
🐇✨ Code carrots for all—enough said!

Warning

There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure.

🔧 ESLint

If the error stems from missing dependencies, add them to the package.json file. For unrecoverable errors (e.g., due to private dependencies), disable the tool in the CodeRabbit configuration.

components/metabase/actions/create-dashboard/create-dashboard.mjs

Oops! Something went wrong! :(

ESLint: 8.57.1

Error [ERR_MODULE_NOT_FOUND]: Cannot find package 'jsonc-eslint-parser' imported from /eslint.config.mjs
at Object.getPackageJSONURL (node:internal/modules/package_json_reader:255:9)
at packageResolve (node:internal/modules/esm/resolve:767:81)
at moduleResolve (node:internal/modules/esm/resolve:853:18)
at defaultResolve (node:internal/modules/esm/resolve:983:11)
at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:801:12)
at #cachedDefaultResolve (node:internal/modules/esm/loader:725:25)
at ModuleLoader.resolve (node:internal/modules/esm/loader:708:38)
at ModuleLoader.getModuleJobForImport (node:internal/modules/esm/loader:309:38)
at #link (node:internal/modules/esm/module_job:202:49)

components/metabase/actions/get-database/get-database.mjs

Oops! Something went wrong! :(

ESLint: 8.57.1

Error [ERR_MODULE_NOT_FOUND]: Cannot find package 'jsonc-eslint-parser' imported from /eslint.config.mjs
at Object.getPackageJSONURL (node:internal/modules/package_json_reader:255:9)
at packageResolve (node:internal/modules/esm/resolve:767:81)
at moduleResolve (node:internal/modules/esm/resolve:853:18)
at defaultResolve (node:internal/modules/esm/resolve:983:11)
at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:801:12)
at #cachedDefaultResolve (node:internal/modules/esm/loader:725:25)
at ModuleLoader.resolve (node:internal/modules/esm/loader:708:38)
at ModuleLoader.getModuleJobForImport (node:internal/modules/esm/loader:309:38)
at #link (node:internal/modules/esm/module_job:202:49)

components/metabase/actions/get-dashboard/get-dashboard.mjs

Oops! Something went wrong! :(

ESLint: 8.57.1

Error [ERR_MODULE_NOT_FOUND]: Cannot find package 'jsonc-eslint-parser' imported from /eslint.config.mjs
at Object.getPackageJSONURL (node:internal/modules/package_json_reader:255:9)
at packageResolve (node:internal/modules/esm/resolve:767:81)
at moduleResolve (node:internal/modules/esm/resolve:853:18)
at defaultResolve (node:internal/modules/esm/resolve:983:11)
at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:801:12)
at #cachedDefaultResolve (node:internal/modules/esm/loader:725:25)
at ModuleLoader.resolve (node:internal/modules/esm/loader:708:38)
at ModuleLoader.getModuleJobForImport (node:internal/modules/esm/loader:309:38)
at #link (node:internal/modules/esm/module_job:202:49)

  • 2 others
✨ 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
🪧 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.
    • Explain this complex logic.
    • 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 explain this code block.
    • @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 explain its main purpose.
    • @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.

Support

Need 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)

  • @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 generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @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.

Copy link
Contributor

@coderabbitai coderabbitai bot left a 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 (1)
components/metabase/package.json (1)

15-17: Pin @pipedream/platform dependency for deterministic builds

The caret (^3.1.0) allows any future 3.x release, which could introduce unintended breaking changes. Consider pinning to the exact version or updating the range only when intentionally upgrading.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between eccf8d3 and be3c4eb.

📒 Files selected for processing (6)
  • components/metabase/actions/create-dashboard/create-dashboard.mjs (1 hunks)
  • components/metabase/actions/get-dashboard/get-dashboard.mjs (1 hunks)
  • components/metabase/actions/get-database/get-database.mjs (1 hunks)
  • components/metabase/actions/run-query/run-query.mjs (2 hunks)
  • components/metabase/metabase.app.mjs (1 hunks)
  • components/metabase/package.json (1 hunks)
🧰 Additional context used
🧠 Learnings (4)
components/metabase/package.json (1)

Learnt from: jcortes
PR: #14935
File: components/sailpoint/package.json:15-18
Timestamp: 2024-12-12T19:23:09.039Z
Learning: When developing Pipedream components, do not add built-in Node.js modules like fs to package.json dependencies, as they are native modules provided by the Node.js runtime.

components/metabase/actions/create-dashboard/create-dashboard.mjs (1)

Learnt from: jcortes
PR: #14467
File: components/gainsight_px/actions/create-account/create-account.mjs:4-6
Timestamp: 2024-10-30T15:24:39.294Z
Learning: In components/gainsight_px/actions/create-account/create-account.mjs, the action name should be "Create Account" instead of "Create Memory".

components/metabase/actions/get-dashboard/get-dashboard.mjs (1)

Learnt from: jcortes
PR: #14467
File: components/gainsight_px/actions/create-account/create-account.mjs:4-6
Timestamp: 2024-10-30T15:24:39.294Z
Learning: In components/gainsight_px/actions/create-account/create-account.mjs, the action name should be "Create Account" instead of "Create Memory".

components/metabase/actions/run-query/run-query.mjs (3)

Learnt from: GTFalcao
PR: #12731
File: components/hackerone/actions/get-members/get-members.mjs:3-28
Timestamp: 2024-07-04T18:11:59.822Z
Learning: When exporting a summary message in the run method of an action, ensure the message is correctly formatted. For example, in the hackerone-get-members action, the correct format is Successfully retrieved ${response.data.length} members.

Learnt from: GTFalcao
PR: #12731
File: components/hackerone/actions/get-members/get-members.mjs:3-28
Timestamp: 2024-10-08T15:33:38.240Z
Learning: When exporting a summary message in the run method of an action, ensure the message is correctly formatted. For example, in the hackerone-get-members action, the correct format is Successfully retrieved ${response.data.length} members.

Learnt from: jcortes
PR: #14467
File: components/gainsight_px/actions/create-account/create-account.mjs:4-6
Timestamp: 2024-10-30T15:24:39.294Z
Learning: In components/gainsight_px/actions/create-account/create-account.mjs, the action name should be "Create Account" instead of "Create Memory".

🧬 Code Graph Analysis (1)
components/metabase/actions/run-query/run-query.mjs (1)
components/metabase/actions/get-dashboard/get-dashboard.mjs (1)
  • response (24-27)
⏰ 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). (4)
  • GitHub Check: Publish TypeScript components
  • GitHub Check: Lint Code Base
  • GitHub Check: Verify TypeScript components
  • GitHub Check: pnpm publish
🔇 Additional comments (9)
components/metabase/actions/get-database/get-database.mjs (1)

7-7: LGTM: Version increment aligns with coordinated package update.

The version bump from "0.0.1" to "0.0.2" is consistent with the broader Metabase component updates in this PR.

components/metabase/metabase.app.mjs (1)

139-139: Approve: Endpoint path updated to /api/card/{id}/query

This change aligns with the official Metabase API, which uses /api/card/{id}/query for standard card queries (the /api/card/pivot/{id}/query endpoint is reserved for pivot tables).

• components/metabase/metabase.app.mjs – line 139: path now /card/${cardId}/query

No further action required.

components/metabase/actions/get-dashboard/get-dashboard.mjs (1)

7-7: LGTM: Consistent version update.

Version increment aligns with the coordinated Metabase component updates.

components/metabase/actions/create-dashboard/create-dashboard.mjs (1)

8-8: LGTM: Version increment is consistent.

The version update aligns with other Metabase action components in this PR.

components/metabase/actions/run-query/run-query.mjs (4)

6-6: Excellent: Description URL updated to match corrected endpoint.

The documentation URL now correctly points to /api/card/{card-id}/query instead of the previous pivot endpoint, aligning with the endpoint correction in metabase.app.mjs.


7-7: LGTM: Version increment is consistent.

Version update aligns with other Metabase action components.


23-35: Well-structured addition of optional properties.

The new dashboardId and collectionPreview properties are properly defined:

  • Both are correctly marked as optional
  • dashboardId reuses the existing propDefinition from the app
  • collectionPreview has appropriate type and descriptive labels
  • Consistent formatting and structure with existing properties

42-43: Proper implementation of new optional properties.

The new properties are correctly:

  • Destructured from the component instance
  • Mapped to snake_case format (dashboard_id, collection_preview) in the API payload
  • Passed to the runCardQuery method consistently with existing patterns

Also applies to: 51-52

components/metabase/package.json (1)

3-3: All Metabase action versions are consistent
Every .mjs under components/metabase/actions is at version 0.0.2—no mismatches found.

@vunguyenhung vunguyenhung merged commit 610723c into master Jul 22, 2025
11 checks passed
@vunguyenhung vunguyenhung deleted the issue-17343 branch July 22, 2025 04:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[BUG] Metabase Run Query component using incorrect endpoint

3 participants