-
Notifications
You must be signed in to change notification settings - Fork 0
fix(sidecar): force JSON response_format on OpenRouter calls #72
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
Oops, something went wrong.
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.
suggestion (testing): Ajouter un test négatif pour un fournisseur qui n’est ni Ollama ni OpenRouter mais qui utilise tout de même le chemin de compatibilité
Actuellement, nous vérifions uniquement l’omission de
response_formatpourprovider="ollama"(ainsi que pour le cassynthesize). Merci d’ajouter également un test négatif pour un autre fournisseur qui utilise le même chemin*_openai_compat(par exempleprovider="openai"ou un fournisseur compatible Anthropic) afin de vérifier qu’il ne reçoit pas non plusresponse_formatdanscall.kwargs. Cela verrouillera le contrat selon lequel seulprovider=="openrouter"bénéficie du mode JSON et évitera d’élargir accidentellement ce comportement.Original comment in English
suggestion (testing): Add a negative test for a non-Ollama, non-OpenRouter provider that still uses the compat path
Currently we only assert omission of
response_formatforprovider="ollama"(plus thesynthesizecase). Please also add a negative test for another provider that uses the same*_openai_compatpath (e.g.provider="openai"or an Anthropic-compat provider) to verify it also does not receiveresponse_formatincall.kwargs. This will lock in the contract that onlyprovider=="openrouter"gets JSON mode and prevent accidental broadening of this behavior.