Skip to content

Conversation

@HavenDV
Copy link
Contributor

@HavenDV HavenDV commented Jul 31, 2025

Summary by CodeRabbit

  • New Features

    • Expanded task parameter options for LeMUR tasks, allowing users to provide transcript IDs or raw input text.
    • Added new configurable options, including model selection, output size, and temperature settings.
  • Documentation

    • Updated schema examples and required fields to reflect the expanded task parameters.

@coderabbitai
Copy link

coderabbitai bot commented Jul 31, 2025

Walkthrough

The schema for LemurTaskParams in the OpenAPI specification was refactored to explicitly include properties from LemurBaseParams, removing inheritance and making fields like final_model required. The schema now directly lists all relevant parameters, and the example was updated to remove the context field.

Changes

Cohort / File(s) Change Summary
OpenAPI Schema Refactor
src/libs/AssemblyAI/openapi.yaml
Refactored LemurTaskParams to declare all properties explicitly, merged in fields from LemurBaseParams, updated required fields and example.

Sequence Diagram(s)

sequenceDiagram
    participant Client
    participant API (LemurTaskParams)
    Client->>API (LemurTaskParams): Submit request with prompt, final_model, transcript_ids/input_text, etc.
    API (LemurTaskParams)-->>Client: Validate required fields (prompt, final_model), process request
Loading

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Poem

A schema grows, its roots now seen,
No more inheritance in between.
Fields explicit, clear and bright,
Lemur tasks now set just right.
With prompt and model, off we go—
A YAML hop in schema flow!
🐇✨

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

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 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.

@HavenDV HavenDV enabled auto-merge (squash) July 31, 2025 18:32
@coderabbitai coderabbitai bot changed the title feat:@coderabbitai feat:Refactor LemurTaskParams schema to inline properties and update example Jul 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 eaafad3 and d65ee75.

⛔ 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 context used
🧬 Code Graph Analysis (1)
src/libs/AssemblyAI/openapi.yaml (2)
src/libs/AssemblyAI/Conversions/LemurTaskParams.cs (2)
  • struct (5-36)
  • FromPrompt (25-35)
src/libs/AssemblyAI/Conversions/LemurTaskParamsVariant1.cs (2)
  • FromPrompt (24-30)
  • LemurTaskParamsVariant1 (5-31)
🔇 Additional comments (1)
src/libs/AssemblyAI/openapi.yaml (1)

5647-5685: Avoid copy-pasting LemurBaseParams – keep the allOf reference instead.

By inlining transcript_ids, input_text, final_model, max_output_size, and temperature here we now maintain the same set of fields in two places (LemurBaseParams and LemurTaskParams).
That creates an inevitable drift risk and doubles the surface for future edits.

A minimal change that still lets you mark final_model as required (your apparent goal) is:

components:
  schemas:
    LemurTaskParams:
      allOf:
        - type: object
          required: [prompt]
          properties:
            prompt:
              type: string
              description: 
        - $ref: '#/components/schemas/LemurBaseParams'
      required: [final_model]   # << extra requirement layered on top

This keeps the single-source-of-truth in LemurBaseParams, prevents drift, and keeps downstream SDK generation simpler.
[ suggest_essential_refactor ]

Comment on lines +5664 to +5670
x-label: Final model
description: |
The model that is used for the final prompt after compression is performed.
default: "default"
oneOf:
- $ref: "#/components/schemas/LemurModel"
max_output_size:
Copy link

Choose a reason for hiding this comment

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

⚠️ Potential issue

final_model type was unintentionally narrowed – restores old behaviour

LemurBaseParams/final_model accepts either an enumerated model OR any arbitrary string via:

anyOf:
  - $ref: '#/components/schemas/LemurModel'
  - type: string

The new definition replaces that with a oneOf that only allows the enum, silently breaking every existing client that was sending a custom model slug.

-              oneOf:
-                - $ref: "#/components/schemas/LemurModel"
+              anyOf:
+                - $ref: "#/components/schemas/LemurModel"
+                - type: string

Please restore the union or this will be a breaking change in the public contract.

🤖 Prompt for AI Agents
In src/libs/AssemblyAI/openapi.yaml around lines 5664 to 5670, the type
definition for final_model was changed from a union allowing either a LemurModel
enum or any string to a oneOf that only allows the enum, which breaks existing
clients using custom strings. To fix this, revert the type definition to use
anyOf with both the LemurModel reference and a string type, restoring the
original union behavior and preventing breaking changes.

@HavenDV HavenDV closed this Aug 1, 2025
auto-merge was automatically disabled August 1, 2025 10:52

Pull request was closed

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