[bot] Re-generate JavaScript client

[openmeterbot]

This PR was automatically generated.

Summary by CodeRabbit

• New Features
  • Introduced new API endpoints for managing plan add-ons, enabling users to list, create, retrieve, update, and delete add-on assignments.
  • Enhanced support with clear data structures for plan add-on details, improving the overall management experience.

[coderabbitai]

📝 Walkthrough

Walkthrough

The pull request updates the API client schema by introducing new endpoints for managing plan add-ons. It adds two new paths with various HTTP methods for listing, creating, retrieving, updating, and deleting plan add-ons. Additionally, the update includes new components specifying the structure for plan add-ons and corresponding operations in the API interface.

Changes

File Path

Change Summary

api/.../schemas.ts

Added two new endpoints: /api/v1/plans/{planId}/addons (with GET for listing and POST for creating add-ons) and /api/v1/plans/{planId}/addons/{planAddonId} (with GET for retrieving, PUT for updating, and DELETE for removing add-ons). Introduced new components (PlanAddon, PlanAddonCreate, PlanAddonReplaceUpdate) and operations (listPlanAddons, createPlanAddon, getPlanAddon, updatePlanAddon, deletePlanAddon) in the API schema.

Tip

⚡💬 Agentic Chat (Pro Plan, General Availability)

• We're introducing multi-step agentic chat in review comments and issue comments, within and outside of PR's. This feature enhances review and issue discussions with the CodeRabbit agentic chat by enabling advanced interactions, including the ability to create pull requests directly from comments and add commits to existing pull requests.

---

📜 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 dfc43fa and fcf6762.

📒 Files selected for processing (1)

• api/client/javascript/src/client/schemas.ts (4 hunks)

🧰 Additional context used

🧬 Code Graph Analysis (1)

api/client/javascript/src/client/schemas.ts (2)

api/api.gen.go (3)

• PlanAddon (4763-4794)
• PlanAddonCreate (4797-4819)
• PlanAddonReplaceUpdate (4822-4844)

api/client/go/client.gen.go (3)

• PlanAddon (4459-4490)
• PlanAddonCreate (4493-4515)
• PlanAddonReplaceUpdate (4518-4540)

⏰ Context from checks skipped due to timeout of 90000ms (12)

• GitHub Check: Artifacts / Container image
• GitHub Check: E2E
• GitHub Check: CI
• GitHub Check: Quickstart
• GitHub Check: Developer environment
• GitHub Check: Commit hooks
• GitHub Check: Lint
• GitHub Check: Migration Checks
• GitHub Check: Test
• GitHub Check: Build
• GitHub Check: Analyze (javascript)
• GitHub Check: Analyze (go)

🔇 Additional comments (4)

api/client/javascript/src/client/schemas.ts (4)

7147-7293: Schema definitions for Plan Add-ons appear consistent.
These type definitions and doc comments align well with the corresponding Golang definitions. The usage of read-only fields is clear, and no immediate correctness, performance, or maintainability concerns arise from this.

---

9828-9831: Export statements for new PlanAddon types are correct.
Exporting these new schemas ensures they will be available for client usage. No issues are found.

---

18760-19247:

Details

❓ Verification inconclusive

Verify integration and test coverage for new plan add-on operations.
These newly introduced operations—listPlanAddons, createPlanAddon, getPlanAddon, updatePlanAddon, and deletePlanAddon—are thoroughly specified with proper status codes and documentation. Please confirm that they're exercised in client integration tests or e2e tests to guard against regressions.

As a follow-up, you can run a script to find any test references to these operations:

---

🏁 Script executed:

#!/bin/bash
# Searches for references to all newly added plan add-on operations in your JS client test folder
fd -t f --glob "test*.?(js|ts)" --exec rg "listPlanAddons|createPlanAddon|getPlanAddon|updatePlanAddon|deletePlanAddon" {}

Length of output: 126

---

Attention: Please Verify Test Coverage for New Plan Add-on Operations Manually
The new operations (listPlanAddons, createPlanAddon, getPlanAddon, updatePlanAddon, and deletePlanAddon) are correctly specified with comprehensive response definitions. However, our automated search for references in the client test files returned no results. Please confirm manually that these endpoints are exercised in the integration or e2e tests to avoid potential regressions.

• Verify that tests exist which call these operations.
• If not, consider adding tests to ensure full coverage.

---

1377-1430:

Details

❓ Verification inconclusive

Encourage adding or verifying test coverage for new plan add-ons path.
The newly introduced '/api/v1/plans/{planId}/addons' route looks correct in terms of structure and documentation. To ensure quality, consider adding or confirming integration tests covering both the listPlanAddons and createPlanAddon endpoints.

Below is a sample script to locate existing or missing test references for these endpoints in your JS client test folder:

---

🏁 Script executed:

#!/bin/bash
# Searches for references to 'listPlanAddons' or 'createPlanAddon' in the test directory
fd -t f --glob "test*.?(js|ts)" --exec rg "listPlanAddons|createPlanAddon" {}

Length of output: 81

---

Ensure Test Coverage for New Plan Add-ons Endpoints

The new routes in api/client/javascript/src/client/schemas.ts (lines 1377–1430) are structured correctly and carry proper documentation. However, our automated search for references to the listPlanAddons and createPlanAddon endpoints in test files did not return any results. Please manually verify if these endpoints are indeed exercised in any tests outside the usual test*.js/ts files; if no tests exist, it is recommended to add comprehensive integration tests to cover these functionalities.

✨ 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

• 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.
  • 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 generate docstrings to generate docstrings for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai plan to trigger planning for file edits and PR creation.
• @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.