Skip to content

Conversation

andrewjschuang
Copy link
Collaborator

@andrewjschuang andrewjschuang commented Jul 30, 2025

WHY

Summary by CodeRabbit

  • New Features

    • Improved Google Sheets integration with an option to filter spreadsheets by ownership when selecting a sheet.
  • Chores

    • Updated version numbers for multiple Google Sheets actions and sources to reflect the latest release. No changes to functionality or user experience in these updates.

Copy link

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

Copy link
Contributor

coderabbitai bot commented Jul 30, 2025

Walkthrough

This update consists primarily of version number increments across multiple Google Sheets action and source components, as well as the package manifest. The only functional change is in the main app file, where the listSheetsOptions method and its usage now support an optional fetchOnlyOwned parameter to filter spreadsheets by ownership.

Changes

Cohort / File(s) Change Summary
Google Sheets Action Components: Version Bumps
components/google_sheets/actions/*/*.mjs
Incremented version numbers in the default export objects of all listed Google Sheets action modules. No logic or structural changes.
Google Sheets Source Components: Version Bumps
components/google_sheets/sources/*/*.mjs
Incremented version numbers in the default export objects of all listed Google Sheets source modules. No logic or structural changes.
Package Manifest
components/google_sheets/package.json
Updated package version from 0.8.5 to 0.8.6.
Google Sheets App: Ownership Filter
components/google_sheets/google_sheets.app.mjs
Added fetchOnlyOwned parameter to sheetID.options and listSheetsOptions to optionally filter spreadsheets by owner.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant sheetID.options
    participant listSheetsOptions
    participant Google Drive API

    User->>sheetID.options: Call with (query, fetchOnlyOwned)
    sheetID.options->>listSheetsOptions: Pass (driveId, pageToken, query, fetchOnlyOwned)
    listSheetsOptions->>Google Drive API: Query spreadsheets (optionally filter by owner)
    Google Drive API-->>listSheetsOptions: Return spreadsheet list
    listSheetsOptions-->>sheetID.options: Return filtered options
    sheetID.options-->>User: Return available spreadsheet options
Loading

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~6 minutes

Poem

A hop, a skip, a version hop,
Each module gets a shiny top.
One new filter, clean and keen,
Finds just the sheets that you have seen.
The garden’s neat, the carrots grown,
Updates shipped—by rabbits sown! 🥕✨

Note

⚡️ Unit Test Generation is now available in beta!

Learn more here, or try it out under "Finishing Touches" below.

✨ Finishing Touches
  • 📝 Generate Docstrings
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch google-sheets-fix-list-sheets-shared-drive

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 generate unit tests to generate unit tests for 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.

@andrewjschuang andrewjschuang merged commit 4d5dafb into master Jul 30, 2025
10 of 11 checks passed
@andrewjschuang andrewjschuang deleted the google-sheets-fix-list-sheets-shared-drive branch July 30, 2025 22:04
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 (5)
components/google_sheets/actions/clear-cell/clear-cell.mjs (1)

10-10: Incremented version—remember to update release notes

The patch bump from 0.1.130.1.14 looks fine. Please ensure the component-level CHANGELOG (if maintained) reflects this increment so downstream consumers can track the release rationale.

components/google_sheets/actions/get-values-in-range/get-values-in-range.mjs (1)

10-10: Version bump noted—sync documentation

0.1.110.1.12 is OK. Verify that any public docs or marketplace metadata reference the new version to avoid mismatched installation instructions.

components/google_sheets/actions/update-row/update-row.mjs (1)

13-13: Patch version updated—double-check semver intent

Moving to 0.1.13 signals a bug-fix level change. Since no logic changed, confirm that bumping was intentional and aligns with your publishing workflow (e.g., ensuring each monorepo release gets a fresh patch even for meta updates).

components/google_sheets/actions/upsert-row/upsert-row.mjs (1)

27-27: Version increment logged

Patch bump to 0.1.14 acknowledged. Make sure package.json’s dependency map (if any) is updated so consumers pulling @pipedream/[email protected] receive this action version.

components/google_sheets/sources/new-row-added/new-row-added.mjs (1)

11-11: Source version bumped—update sample events if necessary

0.1.14 recorded. If the only change is metadata, the existing sample event remains valid; otherwise refresh sampleEmit to reflect any schema tweaks.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between e67dd18 and 13195e6.

📒 Files selected for processing (28)
  • components/google_sheets/actions/add-column/add-column.mjs (1 hunks)
  • components/google_sheets/actions/add-multiple-rows/add-multiple-rows.mjs (1 hunks)
  • components/google_sheets/actions/add-single-row/add-single-row.mjs (1 hunks)
  • components/google_sheets/actions/clear-cell/clear-cell.mjs (1 hunks)
  • components/google_sheets/actions/clear-rows/clear-rows.mjs (1 hunks)
  • components/google_sheets/actions/copy-worksheet/copy-worksheet.mjs (1 hunks)
  • components/google_sheets/actions/create-spreadsheet/create-spreadsheet.mjs (1 hunks)
  • components/google_sheets/actions/create-worksheet/create-worksheet.mjs (1 hunks)
  • components/google_sheets/actions/delete-rows/delete-rows.mjs (1 hunks)
  • components/google_sheets/actions/delete-worksheet/delete-worksheet.mjs (1 hunks)
  • components/google_sheets/actions/find-row/find-row.mjs (1 hunks)
  • components/google_sheets/actions/get-cell/get-cell.mjs (1 hunks)
  • components/google_sheets/actions/get-spreadsheet-by-id/get-spreadsheet-by-id.mjs (1 hunks)
  • components/google_sheets/actions/get-values-in-range/get-values-in-range.mjs (1 hunks)
  • components/google_sheets/actions/insert-anchored-note/insert-anchored-note.mjs (1 hunks)
  • components/google_sheets/actions/insert-comment/insert-comment.mjs (1 hunks)
  • components/google_sheets/actions/list-worksheets/list-worksheets.mjs (1 hunks)
  • components/google_sheets/actions/update-cell/update-cell.mjs (1 hunks)
  • components/google_sheets/actions/update-multiple-rows/update-multiple-rows.mjs (1 hunks)
  • components/google_sheets/actions/update-row/update-row.mjs (1 hunks)
  • components/google_sheets/actions/upsert-row/upsert-row.mjs (1 hunks)
  • components/google_sheets/google_sheets.app.mjs (2 hunks)
  • components/google_sheets/package.json (1 hunks)
  • components/google_sheets/sources/new-comment/new-comment.mjs (1 hunks)
  • components/google_sheets/sources/new-row-added-polling/new-row-added-polling.mjs (1 hunks)
  • components/google_sheets/sources/new-row-added/new-row-added.mjs (1 hunks)
  • components/google_sheets/sources/new-updates/new-updates.mjs (1 hunks)
  • components/google_sheets/sources/new-worksheet/new-worksheet.mjs (1 hunks)
🧰 Additional context used
🧠 Learnings (7)
components/google_sheets/sources/new-comment/new-comment.mjs (1)

Learnt from: GTFalcao
PR: #15376
File: components/monday/sources/name-updated/name-updated.mjs:6-6
Timestamp: 2025-01-23T03:55:15.166Z
Learning: Source names in Monday.com components don't need to start with "New" if they emit events for updated items (e.g., "Name Updated", "Column Value Updated") rather than new items. This follows the component guidelines exception where the "New" prefix is only required when emits are limited to new items.

components/google_sheets/sources/new-worksheet/new-worksheet.mjs (1)

Learnt from: GTFalcao
PR: #15376
File: components/monday/sources/name-updated/name-updated.mjs:6-6
Timestamp: 2025-01-23T03:55:15.166Z
Learning: Source names in Monday.com components don't need to start with "New" if they emit events for updated items (e.g., "Name Updated", "Column Value Updated") rather than new items. This follows the component guidelines exception where the "New" prefix is only required when emits are limited to new items.

components/google_sheets/actions/create-spreadsheet/create-spreadsheet.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/google_sheets/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/google_sheets/sources/new-row-added-polling/new-row-added-polling.mjs (1)

Learnt from: GTFalcao
PR: #15376
File: components/monday/sources/name-updated/name-updated.mjs:6-6
Timestamp: 2025-01-23T03:55:15.166Z
Learning: Source names in Monday.com components don't need to start with "New" if they emit events for updated items (e.g., "Name Updated", "Column Value Updated") rather than new items. This follows the component guidelines exception where the "New" prefix is only required when emits are limited to new items.

components/google_sheets/sources/new-updates/new-updates.mjs (2)

Learnt from: GTFalcao
PR: #15376
File: components/monday/sources/name-updated/name-updated.mjs:6-6
Timestamp: 2025-01-23T03:55:15.166Z
Learning: Source names in Monday.com components don't need to start with "New" if they emit events for updated items (e.g., "Name Updated", "Column Value Updated") rather than new items. This follows the component guidelines exception where the "New" prefix is only required when emits are limited to new items.

Learnt from: GTFalcao
PR: #14265
File: components/the_magic_drip/sources/common.mjs:35-43
Timestamp: 2024-10-10T19:18:27.998Z
Learning: In components/the_magic_drip/sources/common.mjs, when processing items in getAndProcessData, savedIds is intentionally updated with IDs of both emitted and non-emitted items to avoid emitting retroactive events upon first deployment and ensure only new events are emitted as they occur.

components/google_sheets/sources/new-row-added/new-row-added.mjs (1)

Learnt from: GTFalcao
PR: #15376
File: components/monday/sources/name-updated/name-updated.mjs:6-6
Timestamp: 2025-01-23T03:55:15.166Z
Learning: Source names in Monday.com components don't need to start with "New" if they emit events for updated items (e.g., "Name Updated", "Column Value Updated") rather than new items. This follows the component guidelines exception where the "New" prefix is only required when emits are limited to new items.

🔇 Additional comments (24)
components/google_sheets/google_sheets.app.mjs (2)

67-67: LGTM! Clean parameter addition with proper forwarding.

The new fetchOnlyOwned parameter is correctly added to the destructured options and properly forwarded to the listSheetsOptions method.

Also applies to: 70-70


256-262: LGTM! Proper implementation of ownership filtering.

The implementation correctly:

  • Updates the method signature to accept the fetchOnlyOwned parameter
  • Uses Google Drive API's ownership filter syntax 'me' in owners when enabled
  • Maintains backward compatibility by making the parameter optional
components/google_sheets/sources/new-comment/new-comment.mjs (1)

9-9: LGTM! Appropriate version bump.

The version increment is part of the coordinated release across Google Sheets components.

components/google_sheets/package.json (1)

3-3: LGTM! Appropriate package version increment.

The version bump from 0.8.5 to 0.8.6 correctly reflects the addition of the new fetchOnlyOwned feature following semantic versioning practices.

components/google_sheets/actions/clear-rows/clear-rows.mjs (1)

10-10: LGTM! Coordinated version increment.

The version bump maintains consistency across Google Sheets action components.

components/google_sheets/actions/insert-comment/insert-comment.mjs (1)

7-7: LGTM! Consistent version increment.

The version bump aligns with the coordinated release across Google Sheets components.

components/google_sheets/actions/add-multiple-rows/add-multiple-rows.mjs (1)

14-14: Version bump acknowledged – no additional action required

Only the metadata string is updated from 0.2.12 to 0.2.13; no functional code was touched.

components/google_sheets/actions/create-spreadsheet/create-spreadsheet.mjs (1)

7-7: Version increment confirmed

The change is confined to the component version (0.1.110.1.12). Implementation remains intact.

components/google_sheets/actions/get-cell/get-cell.mjs (1)

10-10: Component version updated correctly

No logic altered; version string bumped to 0.1.12. All good.

components/google_sheets/actions/delete-rows/delete-rows.mjs (1)

7-7: Version bump verified

Metadata update to 0.0.10 only, with no runtime impact.

components/google_sheets/actions/update-cell/update-cell.mjs (1)

10-10: Version string adjusted

Bumped from 0.1.11 to 0.1.12; implementation unchanged.

components/google_sheets/actions/copy-worksheet/copy-worksheet.mjs (1)

7-8: Version bump acknowledged

Patch increment to 0.1.10 keeps semantic-versioning consistency with the other actions and reflects a non-breaking change.

components/google_sheets/actions/delete-worksheet/delete-worksheet.mjs (1)

7-8: Patch version increment looks good

No code-path changes; the 0.1.10 bump aligns with the rest of the suite.

components/google_sheets/actions/list-worksheets/list-worksheets.mjs (1)

7-8: Patch bump verified

0.1.10 is consistent with the coordinated release across actions.

components/google_sheets/actions/create-worksheet/create-worksheet.mjs (1)

7-8: ✅ Version update accepted

Patch bump only; no functional impact observed.

components/google_sheets/actions/add-column/add-column.mjs (1)

7-8: SemVer patch applied correctly

version: "0.1.10" keeps the action in lock-step with the package release.

components/google_sheets/sources/new-worksheet/new-worksheet.mjs (1)

12-12: Version bump looks good

No functional changes introduced here—just the metadata update.

components/google_sheets/actions/get-spreadsheet-by-id/get-spreadsheet-by-id.mjs (1)

7-7: Metadata-only increment – OK

Pure version update; behaviour remains unchanged.

components/google_sheets/actions/find-row/find-row.mjs (1)

10-10: Version update acknowledged

No logic touched; safe to merge.

components/google_sheets/actions/insert-anchored-note/insert-anchored-note.mjs (1)

8-8: Just a patch-level bump

Nothing else changed—looks fine.

components/google_sheets/sources/new-row-added-polling/new-row-added-polling.mjs (1)

11-11: Patch version increment verified

No functional modifications detected.

components/google_sheets/actions/add-single-row/add-single-row.mjs (1)

13-13: Version bump looks correct – confirm CHANGELOG entry

The increment from 2.1.142.1.15 is consistent with the rest of the PR. Just make sure the package-level CHANGELOG (if maintained) reflects the new version and notes the new fetchOnlyOwned option added in the app file so consumers can discover it.

components/google_sheets/actions/update-multiple-rows/update-multiple-rows.mjs (1)

12-12: Minor version bump acknowledged

0.1.110.1.12 is fine. No other changes in this file, so the bump just needs to be documented alongside the new Sheets option introduced in the app component.

components/google_sheets/sources/new-updates/new-updates.mjs (1)

12-12: Source version increment noted

0.2.100.2.11 aligns with the global component patch bump. Nothing else to flag.

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.

1 participant