Expose model capabilities#227
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## trunk #227 +/- ##
============================================
+ Coverage 88.12% 88.21% +0.08%
- Complexity 1213 1227 +14
============================================
Files 60 60
Lines 3934 3964 +30
============================================
+ Hits 3467 3497 +30
Misses 467 467
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message. To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
Summary
Closes #226 Expose model input/output modality capabilities at runtime.
Currently there is no ergonomic way to ask a model instance which input and output modalities it accepts. Developers had to guess from model names (
"transcribe","audio", etc.) or dig through rawSupportedOptionobjects — both fragile approaches.This PR adds three first-class methods to
ModelInterfaceand implements them inAbstractApiBasedModel: