feat:Update OpenAPI spec for consistent dataset listing across SDKs

[HavenDV]

Summary by CodeRabbit

• Documentation
  • Updated OpenAPI specification code samples for Cohere API across multiple programming languages
  • Modified dataset retrieval methods to list datasets instead of fetching by specific ID
  • Updated SDK examples for Go, Python (sync/async), Java, TypeScript, and cURL

[coderabbitai]

Walkthrough

The pull request modifies the OpenAPI specification for the Cohere API, focusing on dataset operations across multiple programming language SDKs. The primary change involves transitioning from retrieving a specific dataset by ID to listing all datasets consistently across Go, Python (sync and async), Java, TypeScript, and cURL implementations. This modification suggests a standardization of dataset retrieval methods across different SDK implementations.

Changes

File	Change Summary
src/libs/Cohere/openapi.yaml	Updated dataset retrieval methods across multiple SDKs from get(id) to list()

Poem

🐰 Datasets dancing, no more solo flight,
List them all with CodeRabbit's might!
From get to list, a hoppy delight,
SDKs united, code shining bright,
Bunny's API magic takes its height! 🌈

---

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

• 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. (Beta)
• @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.

[coderabbitai]

Actionable comments posted: 1

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between aefab52 and 5ad0b64.

📒 Files selected for processing (1)

• src/libs/Cohere/openapi.yaml (2 hunks)

🔇 Additional comments (1)

src/libs/Cohere/openapi.yaml (1)

9276-9288: LGTM! Consistent implementation across SDKs.

The SDK implementations for Go, Python (sync/async), Java, and TypeScript are well-structured and consistent. They all:

• Use the standardized .list() method
• Follow language-specific best practices
• Demonstrate proper error handling (especially in Go)
• Use correct async/await patterns where applicable

[coderabbitai]

⚠️ Potential issue

Fix inconsistent cURL endpoint for getting a specific dataset

The cURL endpoints appear inconsistent:

• List endpoint uses /v1/datasets
• Get endpoint uses /v1/datasets/id where id seems to be a placeholder

For the get endpoint, replace the literal "id" with a placeholder consistent with other examples:

-  --url https://api.cohere.com/v1/datasets/id \
+  --url https://api.cohere.com/v1/datasets/<<datasetId>> \

Also applies to: 9443-9443