Repository navigation
feat: accept a source file on generation assets - #157
Merged
Merged
Conversation
|
🎉 This PR is included in version 1.23.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Some generation models take a source file instead of a prompt, such as a model that measures a music track. This lets a generation asset carry
src.src(a URI) is optional andpromptis no longer required on its own. An asset needs one of them, enforced in the zod output by the same refine the media assets use.typeenum and the responses are unchanged, so existing requests validate as before.Verify:
pnpm build && pnpm test && pnpm test:smoke(75 pass: a src-only asset parses, an asset with neither is rejected).