remove withLabel from playlistId

[tkalejaiye]

WHY

The current Get Playlist Action doesn't work unless a playlist is selected via async options.

Current Behavior:

When a playlist ID is entered via a custom expression or variable, an undefined value gets passed for the playlist ID resulting in a 400 error.

Expected Behavior:

Passing a variable from a previous step or entering a custom expression should function the same as selecting from a dropdown, and properly pass the playlist ID in the API call

Solution:

This PR fixes this by removing a withLabel parameter in the playlistID prop definition and passing playlistId rather than playlistId.value in get-playlist.mjs.

I couldn't find reference to it on the docs, but I suspect when withLabel is set to true, it passes the label of the option along with the value, hence the previous structure of the function in get-playlist.mjs. By removing both, we can now pass playlist IDs by dropdown or custom expression successfully

Summary by CodeRabbit

• Refactor
  • Improved handling of playlist IDs for the "Get a Playlist" action, resulting in more direct input usage.
  • Updated input field for playlist ID to remove the label display.

[vercel]

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

1 Skipped Deployment

Name	Status	Preview	Comments	Updated (UTC)
pipedream-docs-redirect-do-not-edit	⬜️ Ignored (Inspect)			Jul 30, 2025 0:34am

[vercel]

@tkalejaiye is attempting to deploy a commit to the Pipedreamers Team on Vercel.

A member of the Team first needs to authorize it.

[coderabbitai]

Walkthrough

The changes update the Spotify "Get a Playlist" action to use the playlistId directly instead of accessing its .value property. Additionally, the withLabel: true option is removed from the playlistId prop definition in the Spotify app component. No changes are made to exported or public entity signatures.

Changes

Cohort / File(s)	Change Summary
Get Playlist Action Usage Update components/spotify/actions/get-playlist/get-playlist.mjs	Updated to use playlistId directly instead of playlistId.value; incremented action version; adjusted summary export.
Spotify App Prop Definition components/spotify/spotify.app.mjs	Removed withLabel: true from the playlistId prop definition.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~7 minutes

Poem

A playlist hop, a label drops,
The rabbit tweaks and never stops.
No more .value in the way,
The code is clean, hooray, hooray!
Spotify tunes, the flow is neat,
Review complete—now tap your feet! 🎵🐇

Note

⚡️ Unit Test Generation is now available in beta!

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

---

📜 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 a28b6b4 and 7a81698.

📒 Files selected for processing (2)

• components/spotify/actions/get-playlist/get-playlist.mjs (2 hunks)
• components/spotify/spotify.app.mjs (0 hunks)

💤 Files with no reviewable changes (1)

• components/spotify/spotify.app.mjs

🧰 Additional context used

🧠 Learnings (1)

📓 Common learnings

Learnt from: GTFalcao
PR: PipedreamHQ/pipedream#15376
File: components/monday/sources/column-value-updated/column-value-updated.mjs:17-24
Timestamp: 2025-01-23T03:55:51.998Z
Learning: Alert props in Pipedream components are a special case that do not require a label property, and use the 'content' property as a replacement for description.

⏰ 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

🔇 Additional comments (3)

components/spotify/actions/get-playlist/get-playlist.mjs (3)

7-7: LGTM! Version increment follows semantic versioning.

The version increment from "0.0.1" to "0.0.2" is appropriate for this functional fix.

---

26-26: LGTM! Correctly implements the fix for custom expressions and variables.

Passing playlistId directly instead of playlistId.value aligns with the removal of withLabel from the prop definition. This change enables the action to work with custom expressions, variables, and dropdown selections.

---

29-29: LGTM! Summary export is consistent with the core fix.

Using playlistId directly in the summary message maintains consistency with the API call change and ensures the correct playlist ID is displayed regardless of input method.

✨ Finishing Touches

• 📝 Generate Docstrings

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment

---

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

• 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.
  • 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.

[pipedream-component-development]

Thank you so much for submitting this! We've added it to our backlog to review, and our team has been notified.

[pipedream-component-development]

Thanks for submitting this PR! When we review PRs, we follow the Pipedream component guidelines. If you're not familiar, here's a quick checklist:

• Create components to address specific use cases whenever possible
• Component keys should follow the format app_name_slug-slugified-component-name
• Components should follow the standard directory structure
• Prefer Node.js client libraries to REST APIs
• When making API requests, handle pagination to ensure all data / events are processed
• Use secret props to capture sensitive data
• Props and methods should be defined in app files whenever possible
• Document methods with JS Docs
• Use optional props whenever possible, and set a default value where you can
• Use async options to accept user input wherever possible