Skip to content

chore(clerk-js, types): Add clerk.billing.getPlan() #6230

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

Merged

Conversation

panteliselef
Copy link
Member

@panteliselef panteliselef commented Jul 1, 2025

Description

Checklist

  • pnpm test runs as expected.
  • pnpm build runs as expected.
  • (If applicable) JSDoc comments have been added or updated for any package exports
  • (If applicable) Documentation has been updated

Type of change

  • 🐛 Bug fix
  • 🌟 New feature
  • 🔨 Breaking change
  • 📖 Refactoring / dependency upgrade / documentation
  • other:

Summary by CodeRabbit

  • New Features
    • Added the ability to retrieve a specific billing plan by its identifier through a new method in the billing section.

@panteliselef panteliselef requested a review from aeliox July 1, 2025 12:59
@panteliselef panteliselef self-assigned this Jul 1, 2025
Copy link

changeset-bot bot commented Jul 1, 2025

🦋 Changeset detected

Latest commit: 443db0c

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 22 packages
Name Type
@clerk/clerk-js Minor
@clerk/types Minor
@clerk/chrome-extension Patch
@clerk/clerk-expo Patch
@clerk/agent-toolkit Patch
@clerk/astro Patch
@clerk/backend Patch
@clerk/elements Patch
@clerk/expo-passkeys Patch
@clerk/express Patch
@clerk/fastify Patch
@clerk/localizations Patch
@clerk/nextjs Patch
@clerk/nuxt Patch
@clerk/react-router Patch
@clerk/clerk-react Patch
@clerk/remix Patch
@clerk/shared Patch
@clerk/tanstack-react-start Patch
@clerk/testing Patch
@clerk/themes Patch
@clerk/vue Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

Copy link

vercel bot commented Jul 1, 2025

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

Name Status Preview Comments Updated (UTC)
clerk-js-sandbox ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jul 1, 2025 1:00pm

Copy link
Contributor

coderabbitai bot commented Jul 1, 2025

📝 Walkthrough

Walkthrough

This change introduces a new asynchronous method called getPlan to the billing namespace in both the @clerk/clerk-js and @clerk/types packages. The method allows retrieval of a specific commerce plan by its identifier. In the implementation, getPlan fetches a single plan resource from the /commerce/plans/{id} endpoint and returns it as a CommercePlanResource. The method is added to both the CommerceBilling class and the CommerceBillingNamespace interface, complementing the existing functionality for retrieving multiple plans. No additional features or error handling mechanisms are included in this update.


🪧 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 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 (1)
packages/clerk-js/src/core/modules/commerce/CommerceBilling.ts (1)

43-49: LGTM! Implementation follows established patterns.

The getPlan method implementation is consistent with existing methods in the class:

  • Proper async/await usage
  • RESTful endpoint pattern
  • Consistent type casting approach
  • Matches the interface definition exactly

The implementation correctly fetches a single plan by ID and returns a CommercePlan instance.

Consider adding basic input validation for the id parameter to improve robustness:

 getPlan = async (params: { id: string }): Promise<CommercePlanResource> => {
+  if (!params.id?.trim()) {
+    throw new Error('Plan ID is required');
+  }
   const plan = (await BaseResource._fetch({
     path: `/commerce/plans/${params.id}`,
     method: 'GET',
   })) as unknown as CommercePlanJSON;
   return new CommercePlan(plan);
 };
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 524c5e0 and 443db0c.

📒 Files selected for processing (3)
  • .changeset/mean-cougars-obey.md (1 hunks)
  • packages/clerk-js/src/core/modules/commerce/CommerceBilling.ts (2 hunks)
  • packages/types/src/commerce.ts (1 hunks)
🧰 Additional context used
📓 Path-based instructions (6)
`**/*.{js,jsx,ts,tsx}`: All code must pass ESLint checks with the project's conf...

**/*.{js,jsx,ts,tsx}: All code must pass ESLint checks with the project's configuration
Use Prettier for consistent code formatting
Follow established naming conventions (PascalCase for components, camelCase for variables)
Maintain comprehensive JSDoc comments for public APIs
Use dynamic imports for optional features
All public APIs must be documented with JSDoc
Lazy load components and features when possible
Implement proper caching strategies
Use efficient data structures and algorithms
Validate all inputs and sanitize outputs
Implement proper logging with different levels

📄 Source: CodeRabbit Inference Engine (.cursor/rules/development.mdc)

List of files the instruction was applied to:

  • packages/types/src/commerce.ts
  • packages/clerk-js/src/core/modules/commerce/CommerceBilling.ts
`packages/**/*.ts`: TypeScript is required for all packages

packages/**/*.ts: TypeScript is required for all packages

📄 Source: CodeRabbit Inference Engine (.cursor/rules/development.mdc)

List of files the instruction was applied to:

  • packages/types/src/commerce.ts
  • packages/clerk-js/src/core/modules/commerce/CommerceBilling.ts
`packages/**/*.{ts,tsx,d.ts}`: Packages should export TypeScript types alongside runtime code

packages/**/*.{ts,tsx,d.ts}: Packages should export TypeScript types alongside runtime code

📄 Source: CodeRabbit Inference Engine (.cursor/rules/development.mdc)

List of files the instruction was applied to:

  • packages/types/src/commerce.ts
  • packages/clerk-js/src/core/modules/commerce/CommerceBilling.ts
`**/*.{ts,tsx}`: Use proper TypeScript error types

**/*.{ts,tsx}: Use proper TypeScript error types

📄 Source: CodeRabbit Inference Engine (.cursor/rules/development.mdc)

List of files the instruction was applied to:

  • packages/types/src/commerce.ts
  • packages/clerk-js/src/core/modules/commerce/CommerceBilling.ts
`**/*.{ts,tsx}`: Always define explicit return types for functions, especially p...

**/*.{ts,tsx}: Always define explicit return types for functions, especially public APIs
Use proper type annotations for variables and parameters where inference isn't clear
Avoid any type - prefer unknown when type is uncertain, then narrow with type guards
Use interface for object shapes that might be extended
Use type for unions, primitives, and computed types
Prefer readonly properties for immutable data structures
Use private for internal implementation details
Use protected for inheritance hierarchies
Use public explicitly for clarity in public APIs
Prefer readonly for properties that shouldn't change after construction
Use mapped types for transforming object types
Use conditional types for type-level logic
Leverage template literal types for string manipulation
Use ES6 imports/exports consistently
Use default exports sparingly, prefer named exports
Document public functions and APIs with JSDoc-style comments including @param, @returns, @throws, and @example
Define custom error classes for domain-specific errors
Use the Result pattern for error handling instead of throwing exceptions
Use optional chaining and nullish coalescing for safe property access
Let TypeScript infer types when types are obvious
Use const assertions for literal types: as const
Use satisfies operator for type checking without widening
Use readonly arrays and objects for immutability
Use immutable update patterns (spread, etc.) for objects and arrays
Use lazy loading for large types
Prefer unknown over any for performance
Use type-only imports: import type { ... }
Use branded types for domain safety
No any types without justification
Proper error handling with typed errors
Consistent use of readonly for immutable data
Proper generic constraints in TypeScript generics
No unused type parameters in generics
Proper use of utility types instead of manual type construction
Type-only imports where possible for performance
Proper tree-shaking friendly exports
No circular dependencies
Efficient type computations (avoid deep recursion)

📄 Source: CodeRabbit Inference Engine (.cursor/rules/typescript.mdc)

List of files the instruction was applied to:

  • packages/types/src/commerce.ts
  • packages/clerk-js/src/core/modules/commerce/CommerceBilling.ts
`packages/{clerk-js,elements,themes}/**/*`: Visual regression testing should be performed for UI components.

packages/{clerk-js,elements,themes}/**/*: Visual regression testing should be performed for UI components.

📄 Source: CodeRabbit Inference Engine (.cursor/rules/monorepo.mdc)

List of files the instruction was applied to:

  • packages/clerk-js/src/core/modules/commerce/CommerceBilling.ts
🧠 Learnings (2)
📓 Common learnings
Learnt from: dstaley
PR: clerk/javascript#6116
File: .changeset/tangy-garlics-say.md:1-2
Timestamp: 2025-06-13T16:09:53.061Z
Learning: In the Clerk JavaScript repository, contributors create intentionally empty changeset files (containing only the YAML delimiters) when a PR touches only non-published parts of the codebase (e.g., sandbox assets). This signals that no package release is required, so such changesets should not be flagged as missing content.
.changeset/mean-cougars-obey.md (1)
Learnt from: CR
PR: clerk/javascript#0
File: .cursor/rules/monorepo.mdc:0-0
Timestamp: 2025-06-30T10:30:56.197Z
Learning: Applies to packages/@clerk/*/package.json : Framework packages must depend on '@clerk/clerk-js' for core functionality.
🧬 Code Graph Analysis (1)
packages/clerk-js/src/core/modules/commerce/CommerceBilling.ts (3)
packages/types/src/commerce.ts (1)
  • CommercePlanResource (45-66)
packages/types/src/json.ts (1)
  • CommercePlanJSON (613-634)
packages/clerk-js/src/core/resources/CommercePlan.ts (1)
  • CommercePlan (5-83)
⏰ Context from checks skipped due to timeout of 90000ms (5)
  • GitHub Check: semgrep-cloud-platform/scan
  • GitHub Check: Build Packages
  • GitHub Check: Formatting | Dedupe | Changeset
  • GitHub Check: semgrep/ci
  • GitHub Check: Analyze (javascript-typescript)
🔇 Additional comments (3)
.changeset/mean-cougars-obey.md (1)

1-7: LGTM! Well-structured changeset.

The changeset properly documents the minor version bumps for both affected packages with a clear description of the new functionality.

packages/types/src/commerce.ts (1)

13-13: LGTM! Clean interface addition.

The method signature follows TypeScript best practices with explicit typing and is consistent with the existing interface patterns.

packages/clerk-js/src/core/modules/commerce/CommerceBilling.ts (1)

7-7: LGTM! Correct import addition.

The CommercePlanJSON import is properly added to support the type casting in the new getPlan method.

Copy link

pkg-pr-new bot commented Jul 1, 2025

Open in StackBlitz

@clerk/agent-toolkit

npm i https://pkg.pr.new/@clerk/agent-toolkit@6230

@clerk/astro

npm i https://pkg.pr.new/@clerk/astro@6230

@clerk/backend

npm i https://pkg.pr.new/@clerk/backend@6230

@clerk/chrome-extension

npm i https://pkg.pr.new/@clerk/chrome-extension@6230

@clerk/clerk-js

npm i https://pkg.pr.new/@clerk/clerk-js@6230

@clerk/dev-cli

npm i https://pkg.pr.new/@clerk/dev-cli@6230

@clerk/elements

npm i https://pkg.pr.new/@clerk/elements@6230

@clerk/clerk-expo

npm i https://pkg.pr.new/@clerk/clerk-expo@6230

@clerk/expo-passkeys

npm i https://pkg.pr.new/@clerk/expo-passkeys@6230

@clerk/express

npm i https://pkg.pr.new/@clerk/express@6230

@clerk/fastify

npm i https://pkg.pr.new/@clerk/fastify@6230

@clerk/localizations

npm i https://pkg.pr.new/@clerk/localizations@6230

@clerk/nextjs

npm i https://pkg.pr.new/@clerk/nextjs@6230

@clerk/nuxt

npm i https://pkg.pr.new/@clerk/nuxt@6230

@clerk/clerk-react

npm i https://pkg.pr.new/@clerk/clerk-react@6230

@clerk/react-router

npm i https://pkg.pr.new/@clerk/react-router@6230

@clerk/remix

npm i https://pkg.pr.new/@clerk/remix@6230

@clerk/shared

npm i https://pkg.pr.new/@clerk/shared@6230

@clerk/tanstack-react-start

npm i https://pkg.pr.new/@clerk/tanstack-react-start@6230

@clerk/testing

npm i https://pkg.pr.new/@clerk/testing@6230

@clerk/themes

npm i https://pkg.pr.new/@clerk/themes@6230

@clerk/types

npm i https://pkg.pr.new/@clerk/types@6230

@clerk/upgrade

npm i https://pkg.pr.new/@clerk/upgrade@6230

@clerk/vue

npm i https://pkg.pr.new/@clerk/vue@6230

commit: 443db0c

@panteliselef panteliselef merged commit f2a6641 into main Jul 1, 2025
39 of 40 checks passed
@panteliselef panteliselef deleted the elef/com-983-introduce-clerkbillinggetplan-in-clerk-js branch July 1, 2025 13:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants