Skip to content
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

[FEATURE] New prop to Gong action #14690

Merged
merged 1 commit into from
Nov 20, 2024

Conversation

jcortes
Copy link
Collaborator

@jcortes jcortes commented Nov 20, 2024

WHY

Resolves #14683

Summary by CodeRabbit

Release Notes

  • New Features

    • Introduced a new callIds property to filter calls by their IDs in relevant actions.
  • Version Updates

    • Incremented version numbers for multiple actions and modules to reflect updates (e.g., from "0.0.1" to "0.0.2").
  • Dependency Updates

    • Updated the dependency on @pipedream/platform to version ^3.0.3.

@jcortes jcortes added the action New Action Request label Nov 20, 2024
@jcortes jcortes self-assigned this Nov 20, 2024
Copy link

vercel bot commented Nov 20, 2024

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

A member of the Team first needs to authorize it.

Copy link
Contributor

coderabbitai bot commented Nov 20, 2024

Walkthrough

The pull request includes updates to several files within the Gong application, primarily focusing on version increments from "0.0.1" to "0.0.2" for multiple actions and components. Notably, the retrieve-transcripts-of-calls action introduces a new required property, callIds, while the gong.app.mjs file adds an optional callIds property with asynchronous options. Additionally, the package.json file reflects an updated dependency version. Overall, the changes enhance the functionality and version management of the Gong application.

Changes

File Path Change Summary
components/gong/actions/add-new-call/add-new-call.mjs Version updated to "0.0.2".
components/gong/actions/list-calls/list-calls.mjs Version updated to "0.0.2".
components/gong/actions/retrieve-transcripts-of-calls/retrieve-transcripts-of-calls.mjs Version updated to "0.0.2"; added required callIds property; minor message formatting change.
components/gong/gong.app.mjs Added optional callIds property; includes async options method for filtering calls.
components/gong/package.json Version updated to "0.1.1"; dependency on @pipedream/platform updated to "^3.0.3".
components/gong/sources/new-call/new-call.mjs Version updated to "0.0.2".

Assessment against linked issues

Objective Addressed Explanation
Add callIds prop filter with async options to retrieve-transcripts-of-calls action (#14683)

Possibly related PRs

Suggested labels

enhancement

Poem

🐇 In the land of code, where changes bloom,
New props and versions, dispelling the gloom.
With callIds added, our actions take flight,
Enhancing the Gong, making it bright!
So hop along, let the updates unfold,
In the world of tech, new stories are told! 🌼


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ 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.
    • Generate unit testing code for this file.
    • 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 generate unit testing code for this file.
    • @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 generate unit testing code.
    • @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.

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

vercel bot commented Nov 20, 2024

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) Nov 20, 2024 3:13pm

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: 2

🧹 Outside diff range and nitpick comments (1)
components/gong/gong.app.mjs (1)

69-73: LGTM! Consider minor description formatting improvement.

The property definition is well-structured and the type is appropriate for the use case. The description clearly explains the fallback behavior.

Consider using backticks for the parameter names in the description for consistency:

-description: "List of calls Ids to be filtered. If not supplied, returns all calls between **From Date Time** and **To Date Time**.",
+description: "List of calls Ids to be filtered. If not supplied, returns all calls between `From Date Time` and `To Date Time`.",
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between efea192 and 06addf6.

⛔ Files ignored due to path filters (1)
  • pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml
📒 Files selected for processing (6)
  • components/gong/actions/add-new-call/add-new-call.mjs (1 hunks)
  • components/gong/actions/list-calls/list-calls.mjs (1 hunks)
  • components/gong/actions/retrieve-transcripts-of-calls/retrieve-transcripts-of-calls.mjs (3 hunks)
  • components/gong/gong.app.mjs (1 hunks)
  • components/gong/package.json (2 hunks)
  • components/gong/sources/new-call/new-call.mjs (1 hunks)
✅ Files skipped from review due to trivial changes (3)
  • components/gong/actions/add-new-call/add-new-call.mjs
  • components/gong/actions/list-calls/list-calls.mjs
  • components/gong/sources/new-call/new-call.mjs
🔇 Additional comments (6)
components/gong/package.json (1)

13-13: Verify compatibility with @pipedream/platform v3

The major version update of @pipedream/platform (1.x.x → 3.x.x) might introduce breaking changes. Please ensure all platform API usage has been updated accordingly.

components/gong/actions/retrieve-transcripts-of-calls/retrieve-transcripts-of-calls.mjs (4)

8-8: LGTM! Version bump is appropriate.

The version increment from 0.0.1 to 0.0.2 correctly reflects the addition of a new feature (callIds prop).


60-60: LGTM! Improved message formatting.

The addition of a period improves the grammatical correctness of the success message.


32-37: ⚠️ Potential issue

Consider semantic version bump to 0.1.0

Adding a required property is a breaking change as it affects backward compatibility. According to semantic versioning, this should warrant a minor version bump (0.1.0) rather than a patch version bump (0.0.2).

Also, let's verify the prop definition in the app module:


Line range hint 40-46: Verify API endpoint compatibility with callIds filter

The implementation spreads the filter object (including callIds) into the request data. Let's verify this matches the Gong API documentation referenced in the component description.

Also applies to: 51-57

✅ Verification successful

API endpoint implementation appears correct for filter usage

The implementation aligns with the expected behavior:

  • The Gong README confirms the API supports retrieving transcripts as a core functionality
  • The code correctly structures the request by:
    • Using the /calls/transcript endpoint
    • Passing the filter object in the request data, which is the standard way to send filtering parameters
  • The implementation follows the pattern seen in the usage example where the filter is passed within the data object
🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Find API documentation references and usage examples

# Check for API documentation or examples
rg -A 5 'calls/transcript' --type md
rg -A 5 'callIds.*filter' --type js

Length of output: 74


Script:

#!/bin/bash
# Let's try a broader search for API documentation and usage patterns

# Search for any documentation files related to Gong API
fd -e md -e txt . | xargs rg -l "gong.*api|api.*gong" -i

# Search for any references to transcript endpoints
rg -i "transcript.*endpoint|endpoint.*transcript"

# Look for similar implementations or test files
ast-grep --pattern 'post({
  path: "/calls/transcript",
  $$$
})'

# Search for any configuration or constant files that might contain API documentation
fd -e js -e mjs | xargs rg -l "GONG_API|gong.*config" -i

Length of output: 705


Script:

#!/bin/bash
# Let's check the Gong README and any related files for API usage details

# Display content of Gong README
cat components/gong/README.md

# Look for any test files or examples related to transcript retrieval
fd -e test.mjs -e spec.mjs -e test.js -e spec.js | xargs rg -l "transcript"

# Search for any usage examples of the transcript endpoint
rg -A 5 "retrieveTranscriptsOfCalls" 

Length of output: 7978

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

69-83: Verify integration with retrieve-transcripts-of-calls action.

The property is marked as optional here but required in the retrieve-transcripts-of-calls action according to the AI summary. Let's verify this integration.

components/gong/package.json Show resolved Hide resolved
components/gong/gong.app.mjs Show resolved Hide resolved
@lcaresia lcaresia merged commit 8fe1c71 into PipedreamHQ:master Nov 20, 2024
10 of 11 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
action New Action Request
Development

Successfully merging this pull request may close these issues.

[FEATURE] New prop to Gong action
2 participants