Skip to content

Google Sheet - Create Spreadsheet: allow create spreadsheet in a folder #16664

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

michelle0927
Copy link
Collaborator

@michelle0927 michelle0927 commented May 14, 2025

Resolves #16643

Summary by CodeRabbit

  • New Features

    • Added an option to specify a folder within a selected drive when creating a new Google Spreadsheet, allowing more control over where new spreadsheets are saved.
  • Chores

    • Updated the version number for the Google Sheets integration.

Copy link

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

Copy link
Contributor

coderabbitai bot commented May 14, 2025

Walkthrough

An optional folderId property was introduced to the Google Sheets "Create Spreadsheet" action, enabling users to specify a folder for the new spreadsheet. The logic now conditionally moves the spreadsheet into the selected folder or drive. The package version was incremented to reflect these updates.

Changes

File(s) Change Summary
components/google_sheets/actions/create-spreadsheet/create-spreadsheet.mjs Added optional folderId prop; updated logic to place new spreadsheets in specified folders; incremented action version.
components/google_sheets/package.json Bumped package version from 0.8.1 to 0.8.2.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant Action
    participant GoogleSheetsAPI

    User->>Action: Trigger create-spreadsheet (with optional folderId)
    Action->>GoogleSheetsAPI: Create spreadsheet
    GoogleSheetsAPI-->>Action: Spreadsheet details
    alt folderId specified or not "My Drive"
        Action->>GoogleSheetsAPI: Move spreadsheet to folder (folderId or driveId)
        GoogleSheetsAPI-->>Action: Updated spreadsheet metadata
        Action-->>User: Return updated metadata
    else
        Action-->>User: Return spreadsheet details
    end
Loading

Assessment against linked issues

Objective Addressed Explanation
Add optional field to create Google Sheets spreadsheet in a specific folder (#16643)

Suggested reviewers

  • lcaresia

Poem

In a folder or drive, a sheet now can dwell,
With a hop and a skip, it’s placed quite well.
From “My Drive” to a nook you choose,
This bunny’s code brings splendid news!
🐇✨📄

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_sheets/actions/create-spreadsheet/create-spreadsheet.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 packageResolve (node:internal/modules/esm/resolve:839:9)
at moduleResolve (node:internal/modules/esm/resolve:908:18)
at defaultResolve (node:internal/modules/esm/resolve:1038:11)
at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:557:12)
at ModuleLoader.resolve (node:internal/modules/esm/loader:525:25)
at ModuleLoader.getModuleJob (node:internal/modules/esm/loader:246:38)
at ModuleJob._link (node:internal/modules/esm/module_job:126:49)

✨ 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 (2)
components/google_sheets/actions/create-spreadsheet/create-spreadsheet.mjs (2)

79-81: Consider error handling for file updates.

The implementation correctly uses folderId as the primary choice, falling back to drive when needed. However, there's no error handling if the updateFile operation fails.

Consider adding try/catch blocks to handle potential errors during file updates:

-    const spreadsheet = await updateFile(response.spreadsheetId, {
-      addParents: folderId || drive,
-    });
+    try {
+      const spreadsheet = await updateFile(response.spreadsheetId, {
+        addParents: folderId || drive,
+      });
+      
+      return getSpreadsheet(spreadsheet.id);
+    } catch (error) {
+      console.error("Error moving spreadsheet to folder:", error);
+      // Still return the created spreadsheet even if move fails
+      return response;
+    }

83-83: Validate spreadsheet ID.

Consider adding a check to ensure spreadsheet.id exists before attempting to fetch the spreadsheet.

-    return getSpreadsheet(spreadsheet.id);
+    return spreadsheet?.id ? getSpreadsheet(spreadsheet.id) : response;
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 0129ef7 and 4c07ea7.

⛔ Files ignored due to path filters (1)
  • pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml
📒 Files selected for processing (2)
  • components/google_sheets/actions/create-spreadsheet/create-spreadsheet.mjs (4 hunks)
  • components/google_sheets/package.json (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (4)
  • GitHub Check: Verify TypeScript components
  • GitHub Check: pnpm publish
  • GitHub Check: Publish TypeScript components
  • GitHub Check: Lint Code Base
🔇 Additional comments (5)
components/google_sheets/package.json (1)

3-3: Version bump is appropriate.

The version increment from 0.8.1 to a patch version 0.8.2 is suitable for this feature addition since it enhances functionality without breaking existing behavior.

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

7-7: Version number correctly incremented.

The action version bump from 0.1.9 to 0.1.10 aligns with the package version increment and appropriately reflects the non-breaking enhancement.


23-33: Well-structured folder selection property.

The new folderId property is properly implemented as an optional parameter with clear description. The dynamic propDefinition correctly uses the selected drive context to filter available folders.


50-50: Correct property destructuring.

The folderId is properly destructured from the component's properties.


75-77: Logical conditional return.

This condition correctly returns the response immediately when no folder is specified and the drive is "My Drive", avoiding unnecessary API calls.

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.

[ACTION] Google Sheet - Create Spreadsheet: allow create spreadsheet in a folder
2 participants