-
-
Notifications
You must be signed in to change notification settings - Fork 1
feat:Update LemurBaseParams schema documentation for transcript_ids and input_text #94
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
💡 Verification agent
🧩 Analysis chain
Description change leaves the array unconstrained – consider adding a formal
maxItemsor clarifying docsThe previous wording (“100 files or 100 hours”) communicated two independent limits.
After the edit the hours-based limit remains, but the array length is now unspecified.
Because OpenAPI cannot express a duration constraint, clients will infer the only enforced limit is hours and might push thousands of
transcript_idsin one call.If the backend still restricts the list size (e.g. 100 transcripts), add an explicit schema constraint:
items: x-label: Transcript ID type: string format: uuid + maxItems: 100 # hard cap retained from the original specAt minimum, extend the sentence to state whether the number of transcripts is unlimited.
Without this, SDKs and generated docs lose an important contract.
🏁 Script executed:
Length of output: 1958
Add explicit
maxItemsto thetranscript_idsarrayWe confirmed that the
transcript_idsschema insrc/libs/AssemblyAI/openapi.yaml(around lines 5577–5582) lacks amaxItemsconstraint, even though the description still mentions “100 hours” and the original spec enforced a 100-item cap. Without this, generated clients may assume unlimited IDs.Please update the schema as follows:
properties: transcript_ids: x-label: Transcript IDs description: | A list of completed transcripts with text. Up to a maximum of 100 hours. Use either transcript_ids or input_text as input into LeMUR. type: array - items: + items: x-label: Transcript ID type: string format: uuid + maxItems: 100 # enforce the original 100-transcript limitIf the service truly allows unlimited transcript IDs regardless of count, please clarify in the description instead.
🤖 Prompt for AI Agents