feat:Refactor LemurTaskParams schema to remove inheritance and add required fields

[HavenDV]

Summary by CodeRabbit

• New Features
  • Expanded task parameter options with additional fields, including transcript IDs, input text, model selection, output size, and temperature settings.
• Documentation
  • Updated schema documentation to clearly list all available task parameters and required fields.

[coderabbitai]

Walkthrough

The LemurTaskParams schema in the OpenAPI specification was modified to explicitly include properties previously inherited from LemurBaseParams. New required fields were added, inheritance was removed, and the example was updated to reflect these changes.

Changes

Cohort / File(s)	Change Summary
OpenAPI Schema Update src/libs/AssemblyAI/openapi.yaml	Expanded LemurTaskParams to explicitly include properties from LemurBaseParams, updated required fields, removed inheritance, and revised example.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

A schema grows, its roots laid bare,
No more inheritance floating in air.
Properties listed, each in its place,
With required fields now setting the pace.
YAML lines aligned, explicit and neat—
This rabbit finds the change quite sweet! 🐇✨

✨ 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_202507311242

---

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: 1

🔭 Outside diff range comments (1)

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

5643-5656: Potentially breaking removal of context and duplicated definition of inherited props

By in-lining transcript_ids here and dropping the allOf: $ref: LemurBaseParams you have silently lost the context property (and the optional additionalProperties guard) that downstream clients may still rely on.
If the intention is merely to make required fields explicit, keep the inheritance and override required, or add context back explicitly.

+        context:
+          x-label: Context
+          description: Context to provide the model. This can be a string or a free-form JSON value.
+          oneOf:
+            - type: string
+            - type: object
+              additionalProperties: true

🧹 Nitpick comments (1)

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

5676-5685: Redundant range on temperature

A numeric type: number with minimum/maximum is sufficient; specifying format: float is superfluous in OpenAPI 3.1 and confuses some tooling (e.g. openapi-generator).
Safe to drop:

-              format: float

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between eaafad3 and 8557d23.

⛔ Files ignored due to path filters (3)

• src/libs/AssemblyAI/Generated/AssemblyAI.JsonConverters.LemurTaskParams.g.cs is excluded by !**/generated/**
• src/libs/AssemblyAI/Generated/AssemblyAI.Models.LemurTaskParams.g.cs is excluded by !**/generated/**
• src/libs/AssemblyAI/Generated/AssemblyAI.Models.LemurTaskParamsVariant1.g.cs is excluded by !**/generated/**

📒 Files selected for processing (1)

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

🔇 Additional comments (1)

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

5663-5670: final_model now uses oneOf instead of the original anyOf

Changing from anyOf to oneOf narrows validation semantics (previously arbitrary strings were allowed).
Confirm this will not reject existing requests that pass custom model IDs.

If broad compatibility is still desired, keep anyOf:

-              oneOf:
+              anyOf:

[coderabbitai]

🛠️ Refactor suggestion

Missing maximum: 4000 on max_output_size

The description says “up to 4000” but the schema omits an explicit maximum.
Add the bound so generators & validators catch oversize values.

           type: integer
           default: 2000
+          maximum: 4000

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	x-label: Maximum output size
	description: Max output size in tokens, up to 4000
	type: integer
	default: 2000
	temperature:
	x-label: Maximum output size
	description: Max output size in tokens, up to 4000
	type: integer
	default: 2000
	maximum: 4000
	temperature:

🤖 Prompt for AI Agents

In src/libs/AssemblyAI/openapi.yaml around lines 5671 to 5675, the
max_output_size property lacks an explicit maximum constraint despite the
description stating "up to 4000". Add a maximum: 4000 field to the
max_output_size schema to enforce this upper bound in validation and code
generation.