Skip to content

Conversation

@jsendo
Copy link
Contributor

@jsendo jsendo commented May 20, 2025

WHY

Summary by CodeRabbit

  • New Features

    • You can now create a BackendClient instance using only an access token, without requiring OAuth credentials.
  • Documentation

    • Updated the changelog to reflect the new access token authentication feature.
  • Chores

    • Bumped the SDK package version to 1.6.2.

@linear
Copy link

linear bot commented May 20, 2025

@vercel
Copy link

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

@coderabbitai
Copy link
Contributor

coderabbitai bot commented May 20, 2025

Walkthrough

The changes introduce support for initializing the BackendClient with either OAuth credentials or a static access token. The relevant type definitions, class properties, and authentication logic are updated to accommodate this new credential type. Documentation and versioning files are updated to reflect the feature addition.

Changes

File(s) Change Summary
packages/sdk/CHANGELOG.md Added changelog entry for version 1.6.2, documenting support for creating BackendClient with only an access token.
packages/sdk/package.json Bumped version from 1.6.1 to 1.6.2.
packages/sdk/src/server/index.ts Updated BackendClientOpts to accept access token credentials; modified BackendClient to support static tokens.

Sequence Diagram(s)

sequenceDiagram
    participant Caller
    participant BackendClient

    Caller->>BackendClient: new BackendClient({ credentials })
    alt credentials has accessToken
        BackendClient->>BackendClient: Store staticAccessToken
    else credentials is OAuthCredentials
        BackendClient->>BackendClient: Initialize oauthClient
    end

    Caller->>BackendClient: authHeaders()
    alt staticAccessToken present
        BackendClient-->>Caller: return Bearer staticAccessToken
    else
        BackendClient->>BackendClient: ensureValidOauthAccessToken()
        BackendClient-->>Caller: return Bearer OAuth token
    end
Loading

Poem

A token in paw, the backend hops in,
Now static or OAuth, both ways you can begin!
With headers so tidy, and options anew,
The client’s more clever—hats off to the crew!
1.6.2, a leap forward in code,
The rabbit approves as down the path it strode.
🐇✨

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.

packages/sdk/src/server/index.ts

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:799:12)
at #cachedDefaultResolve (node:internal/modules/esm/loader:723:25)
at ModuleLoader.resolve (node:internal/modules/esm/loader:706:38)
at ModuleLoader.getModuleJobForImport (node:internal/modules/esm/loader:307:38)
at #link (node:internal/modules/esm/module_job:163:49)

Note

⚡️ AI Code Reviews for VS Code, Cursor, Windsurf

CodeRabbit now has a plugin for VS Code, Cursor and Windsurf. This brings AI code reviews directly in the code editor. Each commit is reviewed immediately, finding bugs before the PR is raised. Seamless context handoff to your AI code agent ensures that you can easily incorporate review feedback.
Learn more here.


Note

⚡️ Faster reviews with caching

CodeRabbit now supports caching for code and dependencies, helping speed up reviews. This means quicker feedback, reduced wait times, and a smoother review experience overall. Cached data is encrypted and stored securely. This feature will be automatically enabled for all accounts on May 16th. To opt out, configure Review - Disable Cache at either the organization or repository level. If you prefer to disable all data retention across your organization, simply turn off the Data Retention setting under your Organization Settings.
Enjoy the performance boost—your workflow just got faster.

✨ 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)
packages/sdk/src/server/index.ts (2)

181-183: Update the documentation for createBackendClient function.

The TSDoc comment for createBackendClient only shows an example with OAuth credentials but should also include an example with static access token for completeness.

 * Creates a new instance of BackendClient with the provided options.
 *
 *
 * @example
 *
 *
 * ```typescript
      const serverClient = createBackendClient({
        environment: "development",
        projectId: "<project id>",
        credentials: {
          clientId: "<client id>",
          clientSecret: "<client secret>",
        },
      })
 * ```
+*
+* @example
+*
+* ```typescript
+*     const serverClient = createBackendClient({
+*       environment: "development",
+*       projectId: "<project id>",
+*       credentials: {
+*         accessToken: "<access token>",
+*       },
+*     })
+* ```
 *
 * @param opts - The options for creating the server client.
 * @returns A new instance of ServerClient.

29-42: Add documentation for the new credential type.

The TSDoc comment for BackendClientOpts.credentials should be updated to document both authentication options.

  /**
   * The credentials to use for authentication against the Pipedream API.
+  * This can be either OAuth credentials (clientId and clientSecret) or a static access token.
   */
  credentials: OAuthCredentials | {
    accessToken: string;
  };
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
Cache: Disabled due to data retention organization setting
Knowledge Base: Disabled due to data retention organization setting

📥 Commits

Reviewing files that changed from the base of the PR and between 594ffd4 and 3e03f96.

📒 Files selected for processing (3)
  • packages/sdk/CHANGELOG.md (1 hunks)
  • packages/sdk/package.json (1 hunks)
  • packages/sdk/src/server/index.ts (4 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (3)
  • GitHub Check: Lint Code Base
  • GitHub Check: test
  • GitHub Check: pnpm publish
🔇 Additional comments (8)
packages/sdk/CHANGELOG.md (1)

5-9: LGTM! The changelog entry clearly documents the new feature.

The changelog entry accurately describes the new capability to create a BackendClient with just an AccessToken, which aligns with the implementation changes in the codebase.

packages/sdk/package.json (1)

4-4: Version bump is appropriate for the feature addition.

The version increment from 1.6.1 to 1.6.2 follows semantic versioning principles for adding a new feature in a backward-compatible manner.

packages/sdk/src/server/index.ts (6)

39-41: LGTM! The type definition is properly updated.

The BackendClientOpts.credentials type now accepts either OAuth credentials or a static access token, which enables the new feature described in the changelog.


193-193: Good defensive programming - making oauthClient potentially undefined.

Making the oauthClient potentially undefined is necessary since it may not be initialized when using a static access token.


199-199: LGTM! Required property for the new feature.

Adding staticAccessToken as a class property is necessary to store the static access token when provided in the credentials.


212-216: Proper initialization logic for both auth methods.

The constructor correctly initializes either the static access token or the OAuth client based on the provided credentials.


254-258: LGTM! Auth headers now support both authentication methods.

The authHeaders method now properly uses the static access token when available, falling back to OAuth authentication otherwise.


262-264: Good defensive check for OAuth client existence.

Adding a check to throw an error if the OAuth client is not configured when trying to use OAuth authentication prevents cryptic errors later.

@jsendo jsendo merged commit 01e8d2e into master May 20, 2025
11 of 12 checks passed
@jsendo jsendo deleted the je/dj-3290-allow-backend-client-to-be-created-with-access-token branch May 20, 2025 19:25
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.

2 participants