Skip to content

Conversation

@michelle0927
Copy link
Collaborator

@michelle0927 michelle0927 commented Jul 10, 2025

Adds a tabIds prop to support returning only the content of the specified tabs.
Requested by user

Summary by CodeRabbit

  • New Features

    • Added an option to select specific tab IDs when retrieving Google Docs content, allowing users to filter and return content from selected tabs only.
  • Bug Fixes

    • Improved validation to ensure tabs content is included when filtering by tab IDs.

@vercel
Copy link

vercel bot commented Jul 10, 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) Visit Preview Jul 10, 2025 9:44pm
pipedream-docs ⬜️ Ignored (Inspect) Jul 10, 2025 9:44pm
pipedream-docs-redirect-do-not-edit ⬜️ Ignored (Inspect) Jul 10, 2025 9:44pm

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Jul 10, 2025

Walkthrough

The changes introduce a new optional tabIds property to the Google Docs "get-document" action, enabling users to filter returned tab content by specific tab IDs. Validation ensures tabIds can only be used when tab content is included. The package version numbers for both the action and its package have been incremented.

Changes

File(s) Change Summary
components/google_docs/actions/get-document/get-document.mjs Added optional tabIds prop with async options, validation logic, and tab filtering in response.
components/google_docs/package.json Bumped package version from 0.4.3 to 0.4.4.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant Action (get-document)
    participant Google Docs API

    User->>Action (get-document): Provide documentId, includeTabsContent, [tabIds]
    Action (get-document)->>Google Docs API: Fetch document (with tabs if includeTabsContent)
    Google Docs API-->>Action (get-document): Return document (with tabs)
    alt tabIds provided & includeTabsContent true
        Action (get-document)->>Action (get-document): Filter tabs by tabIds
    else tabIds provided & includeTabsContent false
        Action (get-document)->>User: Throw ConfigurationError
    end
    Action (get-document)-->>User: Return (filtered) document
Loading

Poem

A hop and a skip through the docs we go,
Now tabs can be filtered, just so you know!
With tabIds in paw, and a version anew,
The document’s content is tailored for you.
🐇✨

"Version bumps and clever checks—
This rabbit brings you fewer specs!"

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/google_docs/actions/get-document/get-document.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)


📜 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 8750df9 and bfdc320.

📒 Files selected for processing (1)
  • components/google_docs/actions/get-document/get-document.mjs (2 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • components/google_docs/actions/get-document/get-document.mjs
⏰ 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). (3)
  • GitHub Check: Publish TypeScript components
  • GitHub Check: Verify TypeScript components
  • GitHub Check: Lint Code Base
✨ 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: 1

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 8f4598a and 8750df9.

⛔ Files ignored due to path filters (1)
  • pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml
📒 Files selected for processing (2)
  • components/google_docs/actions/get-document/get-document.mjs (2 hunks)
  • components/google_docs/package.json (1 hunks)
🧰 Additional context used
🧠 Learnings (1)
components/google_docs/package.json (1)
Learnt from: jcortes
PR: PipedreamHQ/pipedream#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.
⏰ 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: pnpm publish
  • GitHub Check: Lint Code Base
  • GitHub Check: Verify TypeScript components
  • GitHub Check: Publish TypeScript components
🔇 Additional comments (5)
components/google_docs/package.json (1)

3-3: LGTM! Proper semantic versioning.

The version increment from 0.4.3 to 0.4.4 correctly reflects the addition of the new tabIds functionality as a minor feature enhancement.

components/google_docs/actions/get-document/get-document.mjs (4)

2-2: LGTM! Proper import for validation.

The ConfigurationError import is correctly added to support the validation logic for the new tabIds feature.


8-8: LGTM! Proper version increment.

The version increment from 0.1.5 to 0.1.6 correctly reflects the addition of the new tabIds functionality.


41-43: LGTM! Proper validation logic.

The validation correctly ensures that tabIds can only be used when includeTabsContent is true, preventing invalid configurations and providing clear error messaging.


47-49: LGTM! Correct filtering implementation.

The filtering logic correctly filters the tabs array to include only tabs whose tabId matches the provided tabIds list, implementing the expected functionality.

@lcaresia lcaresia moved this from Ready for PR Review to Ready for QA in Component (Source and Action) Backlog Jul 14, 2025
@vunguyenhung vunguyenhung moved this from Ready for QA to In QA in Component (Source and Action) Backlog Jul 15, 2025
@vunguyenhung vunguyenhung moved this from In QA to Ready for Release in Component (Source and Action) Backlog Jul 15, 2025
@vunguyenhung
Copy link
Collaborator

Hi everyone, all test cases are passed! Ready for release!

Test report
https://vunguyenhung.notion.site/Google-Docs-add-tabIds-prop-to-get-document-230bf548bb5e81b9bbcef96e119b009d

@vunguyenhung vunguyenhung merged commit ad84ab1 into master Jul 15, 2025
11 checks passed
@vunguyenhung vunguyenhung deleted the google-docs-select-tabs branch July 15, 2025 00:22
@github-project-automation github-project-automation bot moved this from Ready for Release to Done in Component (Source and Action) Backlog Jul 15, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

4 participants