[Platform] Streamline the models.dev bridge to a data-only layer#2147
Open
chr-hertel wants to merge 1 commit into
Open
[Platform] Streamline the models.dev bridge to a data-only layer#2147chr-hertel wants to merge 1 commit into
chr-hertel wants to merge 1 commit into
Conversation
Reduce the bridge to what is unique to models.dev — the dynamic, independently versioned model catalog — and delegate provider construction and routing to the first-level Platform primitives introduced in PR symfony#1923. * Remove ModelResolver, Factory and BridgeResolver (and the never-wired routing) * ModelCatalog now wires each provider with the model class its bridge expects (e.g. Claude for Anthropic), so it drops directly into the regular bridge * ProviderRegistry::getApiBaseUrl() resolves base URLs via a well-known npm-package fallback for providers whose models.dev entry omits them * Build providers with the regular bridge factories + a models.dev ModelCatalog, and compose them into a Platform that routes via the default CatalogBasedModelRouter
carsonbot
added
Platform
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
2 participants
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.
after #1923 we can fold a lot into the first-level provider/platform setup, so the bridge is basically down to the catalog based on models.dev
am i butchering it too much, could you please check @fabpot?
maybe more controversial changes would be
provider::modelfeature