add lingua_passthrough to router metadata#353
Conversation
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 6120782f2d
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "Codex (@codex) review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "Codex (@codex) address that feedback".
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: a635219d18
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "Codex (@codex) review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "Codex (@codex) address that feedback".
| false, | ||
| false, | ||
| ), | ||
| Err(TransformError::UnsupportedTargetFormat(_)) => (body, None, format, true, true), |
There was a problem hiding this comment.
Distinguish unsupported targets from Lingua pass-through
When the target has no Lingua adapter (for example, ProviderFormat::Mistral is not registered in the adapter registry), transform_request returns UnsupportedTargetFormat after detection, not TransformResult::PassThrough. Marking this as lingua_passthrough = true makes observability report a validated Lingua pass-through even when the router is merely falling back to forwarding the original body unchanged, so unsupported-target fallbacks cannot be separated from real same-format pass-throughs.
Useful? React with 👍 / 👎.
#352