Skip to content

Conversation

@HavenDV
Copy link
Contributor

@HavenDV HavenDV commented May 31, 2025

Summary by CodeRabbit

  • Bug Fixes
    • Updated the API schema to ensure the k parameter in chat endpoints only accepts integer values, improving input validation and consistency.

@coderabbitai
Copy link

coderabbitai bot commented May 31, 2025

Walkthrough

The OpenAPI specification for the Cohere API was updated to change the data type of the k parameter in the /v1/chat and /v2/chat endpoints from a floating-point number to an integer. The format: float attribute was removed, and the type is now explicitly set to integer.

Changes

File Change Summary
src/libs/Cohere/openapi.yaml Changed k parameter type from number (float) to integer for /v1/chat and /v2/chat endpoints.

Poem

In the land of code where schemas dwell,
A number once floated, but now it fell—
From float to int, the change is neat,
Now k stands firm on integer feet.
Hopping along, the API’s clear,
Rabbits rejoice, for type bugs disappear! 🐇✨


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.

@HavenDV HavenDV enabled auto-merge (squash) May 31, 2025 01:47
@HavenDV HavenDV merged commit 6f9d36a into main May 31, 2025
3 of 4 checks passed
@HavenDV HavenDV deleted the bot/update-openapi_202505310146 branch May 31, 2025 01:49
@coderabbitai coderabbitai bot changed the title feat:@coderabbitai feat:Update k parameter type to integer in /v1/chat and /v2/chat endpoints May 31, 2025
Copy link

@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: 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 a4366f5 and 66141a1.

⛔ Files ignored due to path filters (3)
  • src/libs/Cohere/Generated/Cohere.CohereClient.Chatv2.g.cs is excluded by !**/generated/**
  • src/libs/Cohere/Generated/Cohere.ICohereClient.Chatv2.g.cs is excluded by !**/generated/**
  • src/libs/Cohere/Generated/Cohere.Models.Chatv2Request.g.cs is excluded by !**/generated/**
📒 Files selected for processing (1)
  • src/libs/Cohere/openapi.yaml (1 hunks)

Comment on lines 7412 to 7419
k:
maximum: 500
minimum: 0
type: number
type: integer
description: "Ensures that only the top `k` most likely tokens are considered for generation at each step. When `k` is set to `0`, k-sampling is disabled.\nDefaults to `0`, min value of `0`, max value of `500`.\n"
format: float
default: 0
x-fern-audiences:
- public
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Verification agent

🧩 Analysis chain

Replace deprecated float type with integer
This update breaks clients that pass non‐integer values for k. Ensure the old type: number and format: float attributes are fully removed to avoid schema conflicts and treat k exclusively as an integer. Also document this as a breaking change (e.g., bump the API version or note it in the changelog).

Apply this patch if the old definitions still exist above this hunk:

-                  type: number
-                  format: float
+                  type: integer

🏁 Script executed:

#!/bin/bash
# Check for any remaining 'type: number' or 'format: float' in the Cohere OpenAPI spec
rg -n "type: number" src/libs/Cohere/openapi.yaml || echo "No occurrences of 'type: number'"
rg -n "format: float" src/libs/Cohere/openapi.yaml || echo "No occurrences of 'format: float'"

Length of output: 2811


Ensure k uses only integer and document breaking change
The OpenAPI spec still defines k with the deprecated type: number and format: float immediately above the new integer schema (lines 7407–7409), which conflicts with the type: integer at lines 7412–7419 and will break clients sending floats. Remove the old attributes so k is strictly an integer, and note this as a breaking change (bump the API version or add to the changelog).

Affected file: src/libs/Cohere/openapi.yaml
Location: around lines 7407–7409

Apply this patch:

-                  type: number
-                  format: float
+                  type: integer

Committable suggestion skipped: line range outside the PR's diff.

🤖 Prompt for AI Agents
In src/libs/Cohere/openapi.yaml around lines 7407 to 7409, remove the deprecated
'type: number' and 'format: float' attributes for the 'k' parameter to avoid
conflicts with the integer type defined at lines 7412 to 7419. Ensure 'k' is
strictly defined as an integer with the constraints already present.
Additionally, document this as a breaking change by either bumping the API
version or adding a note in the changelog to inform clients about the change in
accepted value types.

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