feat(ai-sdk): export GoogleCacheRegistry + eval fixtures helpers (#46)#47
Merged
Merged
Conversation
Surface the gemstack-internal symbols that the /server provider and ai-eval CLI relocations (#39, #40) need to compile against a published @gemstack/ai-sdk: - GoogleCacheRegistry + GoogleCacheRegistryOptions + CacheStoreLike from the main entry, so a binding can construct the Gemini context-cache registry with its own CacheAdapter. - defaultFixturesDir / readFixture / writeFixture from the ./eval subpath, so an ai-eval binding can read/write recorded fixtures. Purely additive (minor). Prereq for #39 and the ai-eval part of #40.
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
1 participant
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.
Closes #46.
Why
Relocating the
/serverprovider (#39) and theai-evalCLI command (part of #40) to@rudderjs/aiis blocked because the code they move imports gemstack-internal symbols that are not on any public entry, so the inline can't compile against a published@gemstack/ai-sdk:/server'sAiProviderconstructsGoogleCacheRegistry(a runtime class) and wires the app cache into it. A class can't be re-created on the consumer side.commands/ai-evalimportsdefaultFixturesDir/readFixture/writeFixture; the./evalsubpath only re-exportedstepsFromResponse+ theEvalFixturetype.What
Purely additive (minor):
GoogleCacheRegistry+GoogleCacheRegistryOptions+CacheStoreLikefrom the main entry. A binding constructs it with its ownCacheAdapter:new GoogleCacheRegistry({ store }).defaultFixturesDir,readFixture,writeFixturefrom./eval.No behavior change, no new dependency. Build green, all 905 tests pass.
Sequencing
This publishes first, then Rudder inlines
/server+make:agent+ai-eval(#39 / #40), then gemstack removes those subpaths + drops the@rudderjs/core/@rudderjs/consolepeers (#41) - the 3-release sequence noted in the epic (#35).