feat:Add features array to OpenAPI components with x-fern-audiences

[HavenDV]

Summary by CodeRabbit

• New Features
  • Enhanced the public API documentation with a new property that details the supported features of the model.

[coderabbitai]

Walkthrough

A new property named features has been introduced in the components section of the OpenAPI specification within src/libs/Cohere/openapi.yaml. The property is defined as an array of strings representing the features supported by the model and includes the x-fern-audiences attribute to indicate its availability to public audiences.

Changes

File	Change Summary
src/libs/Cohere/openapi.yaml	Added a new property features (array of strings) in the components section with an accompanying x-fern-audiences attribute for public audiences.

Poem

I’m a rabbit with a coding grin,
Hopping through changes, let new features begin.
A shiny array now brightens the view,
With public attributes fresh and new.
Code blossoms like springtime anew!
🐇

---

📜 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 2ad3ceb and 70320cc.

⛔ Files ignored due to path filters (1)

• src/libs/Cohere/Generated/Cohere.Models.GetModelResponse.g.cs is excluded by !**/generated/**

📒 Files selected for processing (1)

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

🔇 Additional comments (1)

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

15695-15701: Proper Addition of the "features" Property

The new "features" property is well defined:

• It correctly specifies the type as an array of strings.
• The items definition and the accompanying description ("The features that the model supports.") clearly communicate the property's intent.
• The inclusion of the x-fern-audiences attribute with a value of - public aligns with the documentation patterns used elsewhere in this section.

Overall, the addition is consistent, clear, and integrates nicely within the OpenAPI specification.

---

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.