feat:Update speakers_expected property descriptions to remove upper limit reference

[HavenDV]

Summary by CodeRabbit

• Documentation
  • Updated the description for the "speakers_expected" setting to remove the previous upper limit, clarifying that there is no specified maximum number of speakers.

[coderabbitai]

Walkthrough

The change updates the description text for the speakers_expected property in two schema locations within the OpenAPI specification file, removing the explicit mention of an upper limit of 10 speakers. No functional or structural modifications are made to the schemas.

Changes

Cohort / File(s)	Change Summary
src/libs/AssemblyAI/openapi.yaml	Updated the description of speakers_expected in the TranscriptOptionalParams and Transcript schemas to remove the "up to 10" limit.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

A tweak to the docs, just a line or two,
No more "up to ten"—the sky’s now in view!
The schema stays steady, constraints out of sight,
Rabbits rejoice in this doc update light.
🐇✨

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch bot/update-openapi_202507280153

---

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.
  • 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 generate unit tests to generate unit tests for 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.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

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

2836-2840: Mirror the earlier description update for consistency

Same comment as above applies to the Transcript schema instance. Make sure any enforced limits are reflected either through explicit maximum/minimum keywords or harmonised documentation, otherwise SDK consumers will be left guessing.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 5995122 and 6e7cba9.

⛔ Files ignored due to path filters (2)

• src/libs/AssemblyAI/Generated/AssemblyAI.Models.Transcript.g.cs is excluded by !**/generated/**
• src/libs/AssemblyAI/Generated/AssemblyAI.Models.TranscriptOptionalParams.g.cs is excluded by !**/generated/**

📒 Files selected for processing (1)

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

🔇 Additional comments (1)

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

1417-1421: Clarify and/or codify any hard limit in the JSON schema

The description update removes the “up to 10” wording, but the schema still does not declare any numeric constraints (minimum, maximum) for speakers_expected.
If the backend still enforces an upper bound (historically 10), callers now receive mixed signals – the docs say “any”, but the API may reject >10. Conversely, if the limit truly no longer exists, references to a hard-coded 10 in the neighbouring speaker_options.max_speakers_expected default and examples become confusing.

Action items

1. Confirm with the service team whether an upper bound is still enforced.
2. Encode the truth in the schema:

# Only if a limit still exists
speakers_expected:
  type: [integer, "null"]
  minimum: 1
  maximum: 10   # or whatever the real ceiling is

3. Audit sibling descriptions (max_speakers_expected, examples, docs) for consistency so that clients and generated SDKs stay in sync.