fix(provider): forward metadata options to cloudflare-ai-gateway provider#15619
Merged
thdxr merged 2 commits intoanomalyco:devfrom Mar 3, 2026
Merged
Conversation
Contributor
|
Thanks for your contribution! This PR doesn't have a linked issue. All PRs must reference an existing issue. Please:
See CONTRIBUTING.md for details. |
- Replace destructuring with dot notation per style guide - Use iife() helper instead of raw IIFE pattern - Remove excessive comments, reduce variable count - Add 2 tests for cloudflare-ai-gateway provider loading and config metadata Fixes anomalyco#15621
Contributor
|
Thanks for updating your PR! It now meets our contributing guidelines. 👍 |
Grappeggia
pushed a commit
to teamslop/slopcode
that referenced
this pull request
Mar 4, 2026
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.
Issue for this PR
Closes #15621
Type of change
What does this PR do?
The
cloudflare-ai-gatewaycustom loader callscreateAiGateway()without forwardingoptions.metadatafrom the provider config. This was introduced in PR #12014 when switching to theai-gateway-providerpackage.The fix reads
metadata,cacheTtl,cacheKey,skipCache, andcollectLogfrominput.optionsand forwards them tocreateAiGateway()when present. It also supports the legacycf-aig-metadataheader (JSON string) as a fallback for existing users who set metadata that way.The
createAiGateway()function already acceptsoptions?: AiGatewayOptions— we just weren't passing them through.How did you verify your code works?
test/provider/provider.test.ts— both verify metadata and options forwardingbun test test/provider/provider.test.tsbun turbo typecheckScreenshots / recordings
Not a UI change.
Checklist