feat(ai): add typed runtime context#628
Open
AlemTuzlak wants to merge 1 commit into
Open
Conversation
Contributor
📝 WalkthroughWalkthroughAdds a generic, typed runtime context channel (TContext) across core types, tool/middleware APIs, chat engine, ChatClient, framework hooks, documentation, examples, E2E fixtures, and tests; context is request-local and not automatically serialized to the model or to the server unless explicitly forwarded/mapped. ChangesTyped Runtime Context Implementation
Estimated code review effort🎯 4 (Complex) | ⏱️ ~75 minutes Possibly related PRs
Suggested reviewers
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
|
AlemTuzlak
force-pushed
the
feat/typed-runtime-context-pr
branch
from
5b10d74 to
fd36fac
Compare
Contributor
🚀 Changeset Version Preview3 package(s) bumped directly, 16 bumped as dependents. 🟩 Patch bumps
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Actionable comments posted: 2
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
packages/typescript/ai/src/activities/chat/middleware/types.ts (1)
384-387:⚠️ Potential issue | 🟠 Major | ⚡ Quick winPropagate
TContextintoonStructuredOutputConfig(and its runner)
packages/typescript/ai/src/activities/chat/middleware/types.tsstill typesonStructuredOutputConfigasctx: ChatMiddlewareContext(non-generic), andpackages/typescript/ai/src/activities/chat/middleware/compose.tsstill typesrunOnStructuredOutputConfigasctx: ChatMiddlewareContext, dropping theTContextparameter fromChatMiddleware<TContext>for this hook.Update both signatures to use
ChatMiddlewareContext<TContext>so the hook receives the correctly typed context.🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@packages/typescript/ai/src/activities/chat/middleware/types.ts` around lines 384 - 387, Update the generic context propagation for the structured-output hook: change the type of onStructuredOutputConfig in the ChatMiddleware<TContext> interface to accept ctx: ChatMiddlewareContext<TContext> (not the non-generic ChatMiddlewareContext), and likewise update the runner function runOnStructuredOutputConfig in compose (and any helper/runner types it uses) to accept ctx: ChatMiddlewareContext<TContext> so the TContext parameter is preserved and the hook receives the correctly typed context.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@examples/ts-react-chat/src/routes/api.tanchat.ts`:
- Around line 164-166: The console.log in the onStart middleware is emitting raw
PII (ctx.context.userId and ctx.context.tenantId); change the log to avoid raw
identifiers by applying a deterministic mask or hash instead (e.g., introduce a
helper like hashIdentifier(id: string) or redactIdentifier(id: string) and call
it for ctx.context.userId and ctx.context.tenantId before logging), or drop
those fields entirely and only log non-PII such as ctx.context.loyaltyTier;
update the console.log invocation in the onStart handler to use the new helper
or redacted values.
In `@examples/ts-react-chat/src/routes/example.runtime-context.tsx`:
- Around line 198-203: The ReactMarkdown instance in example.runtime-context.tsx
incorrectly places the remark plugin remarkGfm in the rehypePlugins list; move
remarkGfm into the remarkPlugins prop so it's applied by remark instead of
rehype (locate the ReactMarkdown component where rehypePlugins is defined and
change the plugin arrays accordingly, keeping rehypeRaw, rehypeSanitize,
rehypeHighlight in rehypePlugins and adding remarkGfm to remarkPlugins).
---
Outside diff comments:
In `@packages/typescript/ai/src/activities/chat/middleware/types.ts`:
- Around line 384-387: Update the generic context propagation for the
structured-output hook: change the type of onStructuredOutputConfig in the
ChatMiddleware<TContext> interface to accept ctx:
ChatMiddlewareContext<TContext> (not the non-generic ChatMiddlewareContext), and
likewise update the runner function runOnStructuredOutputConfig in compose (and
any helper/runner types it uses) to accept ctx: ChatMiddlewareContext<TContext>
so the TContext parameter is preserved and the hook receives the correctly typed
context.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: 601a7093-ba6a-4a21-874d-32f0d2abde34
📒 Files selected for processing (60)
docs/advanced/middleware.mddocs/advanced/runtime-context.mddocs/api/ai-client.mddocs/api/ai-preact.mddocs/api/ai-react.mddocs/api/ai-solid.mddocs/api/ai-svelte.mddocs/api/ai-vue.mddocs/api/ai.mddocs/config.jsondocs/migration/ag-ui-compliance.mddocs/migration/migration-from-vercel-ai.mddocs/tools/client-tools.mddocs/tools/server-tools.mdexamples/ts-code-mode-web/src/lib/execute-prompt.tsexamples/ts-code-mode-web/src/lib/structured-output.tsexamples/ts-react-chat/src/components/Header.tsxexamples/ts-react-chat/src/lib/guitar-tools.tsexamples/ts-react-chat/src/routeTree.gen.tsexamples/ts-react-chat/src/routes/api.tanchat.tsexamples/ts-react-chat/src/routes/example.runtime-context.tsxpackages/typescript/ai-client/src/chat-client.tspackages/typescript/ai-client/src/index.tspackages/typescript/ai-client/src/types.tspackages/typescript/ai-client/tests/chat-client-context.test.tspackages/typescript/ai-client/tests/tool-types.test.tspackages/typescript/ai-code-mode/src/types.tspackages/typescript/ai-code-mode/tests/create-code-mode-tool.test.tspackages/typescript/ai-preact/src/types.tspackages/typescript/ai-preact/src/use-chat.tspackages/typescript/ai-react/src/types.tspackages/typescript/ai-react/src/use-chat.tspackages/typescript/ai-react/tests/use-chat-types.test.tspackages/typescript/ai-solid/src/types.tspackages/typescript/ai-solid/src/use-chat.tspackages/typescript/ai-svelte/src/create-chat.svelte.tspackages/typescript/ai-svelte/src/types.tspackages/typescript/ai-svelte/tests/create-chat-types.test.tspackages/typescript/ai-vue/src/types.tspackages/typescript/ai-vue/src/use-chat.tspackages/typescript/ai/src/activities/chat/index.tspackages/typescript/ai/src/activities/chat/middleware/compose.tspackages/typescript/ai/src/activities/chat/middleware/types.tspackages/typescript/ai/src/activities/chat/tools/tool-calls.tspackages/typescript/ai/src/activities/chat/tools/tool-definition.tspackages/typescript/ai/src/types.tspackages/typescript/ai/src/utilities/chat-params.tspackages/typescript/ai/tests/middleware-context.test.tspackages/typescript/ai/tests/tool-call-manager-context.test.tspackages/typescript/ai/tests/tool-calls-context.test.tspackages/typescript/ai/tests/tool-context.test.tspackages/typescript/ai/tests/type-check.test.tstesting/e2e/fixtures/tools-test/client-context.jsontesting/e2e/fixtures/tools-test/client-server-context.jsontesting/e2e/fixtures/tools-test/server-context.jsontesting/e2e/src/lib/tools-test-tools.tstesting/e2e/src/routes/api.tools-test.tstesting/e2e/src/routes/tools-test.tsxtesting/e2e/tests/tools-test/helpers.tstesting/e2e/tests/tools-test/runtime-context.spec.ts
Comment on lines
+164
to
+166
| console.log( | ||
| `[runtime-context] onStart user=${ctx.context.userId} tenant=${ctx.context.tenantId} tier=${ctx.context.loyaltyTier}`, | ||
| ) |
Contributor
There was a problem hiding this comment.
Avoid logging raw runtime identifiers in middleware logs.
userId and tenantId are written directly to server logs here. Please redact, hash, or drop these fields to reduce PII exposure risk.
🔧 Suggested change
onStart(ctx) {
- console.log(
- `[runtime-context] onStart user=${ctx.context.userId} tenant=${ctx.context.tenantId} tier=${ctx.context.loyaltyTier}`,
- )
+ console.log(
+ `[runtime-context] onStart tier=${ctx.context.loyaltyTier} source=${ctx.context.requestSource}`,
+ )
},📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| console.log( | |
| `[runtime-context] onStart user=${ctx.context.userId} tenant=${ctx.context.tenantId} tier=${ctx.context.loyaltyTier}`, | |
| ) | |
| console.log( | |
| `[runtime-context] onStart tier=${ctx.context.loyaltyTier} source=${ctx.context.requestSource}`, | |
| ) |
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@examples/ts-react-chat/src/routes/api.tanchat.ts` around lines 164 - 166, The
console.log in the onStart middleware is emitting raw PII (ctx.context.userId
and ctx.context.tenantId); change the log to avoid raw identifiers by applying a
deterministic mask or hash instead (e.g., introduce a helper like
hashIdentifier(id: string) or redactIdentifier(id: string) and call it for
ctx.context.userId and ctx.context.tenantId before logging), or drop those
fields entirely and only log non-PII such as ctx.context.loyaltyTier; update the
console.log invocation in the onStart handler to use the new helper or redacted
values.
Comment on lines
+198
to
+203
| rehypePlugins={[ | ||
| rehypeRaw, | ||
| rehypeSanitize, | ||
| rehypeHighlight, | ||
| remarkGfm, | ||
| ]} |
Contributor
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Verify ReactMarkdown plugin wiring in the new runtime-context route.
rg -n -C3 "ReactMarkdown|rehypePlugins|remarkPlugins|remarkGfm" examples/ts-react-chat/src/routes/example.runtime-context.tsxRepository: TanStack/ai
Length of output: 1150
Fix ReactMarkdown plugin wiring: remarkGfm is passed via rehypePlugins
In examples/ts-react-chat/src/routes/example.runtime-context.tsx (ReactMarkdown around lines 198-203), remarkGfm (from remark-gfm) is a remark plugin but is included in rehypePlugins. Move it to remarkPlugins so GFM features work.
🔧 Suggested change
<ReactMarkdown
rehypePlugins={[
rehypeRaw,
rehypeSanitize,
rehypeHighlight,
- remarkGfm,
]}
+ remarkPlugins={[remarkGfm]}
>📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| rehypePlugins={[ | |
| rehypeRaw, | |
| rehypeSanitize, | |
| rehypeHighlight, | |
| remarkGfm, | |
| ]} | |
| <ReactMarkdown | |
| rehypePlugins={[ | |
| rehypeRaw, | |
| rehypeSanitize, | |
| rehypeHighlight, | |
| ]} | |
| remarkPlugins={[remarkGfm]} | |
| > |
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@examples/ts-react-chat/src/routes/example.runtime-context.tsx` around lines
198 - 203, The ReactMarkdown instance in example.runtime-context.tsx incorrectly
places the remark plugin remarkGfm in the rehypePlugins list; move remarkGfm
into the remarkPlugins prop so it's applied by remark instead of rehype (locate
the ReactMarkdown component where rehypePlugins is defined and change the plugin
arrays accordingly, keeping rehypeRaw, rehypeSanitize, rehypeHighlight in
rehypePlugins and adding remarkGfm to remarkPlugins).
|
View your CI Pipeline Execution ↗ for commit fd36fac
☁️ Nx Cloud last updated this comment at |
@tanstack/ai
@tanstack/ai-anthropic
@tanstack/ai-client
@tanstack/ai-code-mode
@tanstack/ai-code-mode-skills
@tanstack/ai-devtools-core
@tanstack/ai-elevenlabs
@tanstack/ai-event-client
@tanstack/ai-fal
@tanstack/ai-gemini
@tanstack/ai-grok
@tanstack/ai-groq
@tanstack/ai-isolate-cloudflare
@tanstack/ai-isolate-node
@tanstack/ai-isolate-quickjs
@tanstack/ai-ollama
@tanstack/ai-openai
@tanstack/ai-openrouter
@tanstack/ai-preact
@tanstack/ai-react
@tanstack/ai-react-ui
@tanstack/ai-solid
@tanstack/ai-solid-ui
@tanstack/ai-svelte
@tanstack/ai-utils
@tanstack/ai-vue
@tanstack/ai-vue-ui
@tanstack/openai-base
@tanstack/preact-ai-devtools
@tanstack/react-ai-devtools
@tanstack/solid-ai-devtools
commit: |
Contributor
There was a problem hiding this comment.
Actionable comments posted: 1
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
packages/typescript/ai/src/activities/chat/middleware/types.ts (1)
349-387:⚠️ Potential issue | 🟠 Major | ⚡ Quick win
onStructuredOutputConfigstill drops typed runtime context
ChatMiddleware<TContext>threadsTContextthrough other hooks, butonStructuredOutputConfigkeepsctx: ChatMiddlewareContext(unknowncontext), so typed context is lost exactly in this phase.Proposed fix
onStructuredOutputConfig?: ( - ctx: ChatMiddlewareContext, + ctx: ChatMiddlewareContext<TContext>, config: StructuredOutputMiddlewareConfig, ) =>🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@packages/typescript/ai/src/activities/chat/middleware/types.ts` around lines 349 - 387, The onStructuredOutputConfig hook currently types its context as ChatMiddlewareContext (losing the generic TContext); update the signature on ChatMiddleware<TContext> so onStructuredOutputConfig receives ctx: ChatMiddlewareContext<TContext> (and keep the existing StructuredOutputMiddlewareConfig type for the second parameter) so the generic runtime context is preserved through this hook; locate the ChatMiddleware interface and change the onStructuredOutputConfig parameter type accordingly (referencing ChatMiddleware, onStructuredOutputConfig, ChatMiddlewareContext, and StructuredOutputMiddlewareConfig).
🧹 Nitpick comments (1)
packages/typescript/ai/tests/middleware-context.test.ts (1)
47-47: ⚡ Quick winAssert reference identity instead of deep equality.
Line 47 currently checks structural equality, so it won’t fail if middleware/tool receive cloned context objects. If the contract is “same runtime context instance,” assert identity with
toBe.Proposed change
- expect(seen).toEqual([context, context]) + expect(seen).toHaveLength(2) + expect(seen[0]).toBe(context) + expect(seen[1]).toBe(context)🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@packages/typescript/ai/tests/middleware-context.test.ts` at line 47, The test currently uses structural equality (expect(seen).toEqual([context, context])) which allows cloned objects to pass; change it to assert reference identity by replacing that assertion with identity checks such as expect(seen[0]).toBe(context) and expect(seen[1]).toBe(context) so both captured entries are the exact same runtime context instance.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@testing/e2e/tests/tools-test/helpers.ts`:
- Around line 94-107: The current page.evaluate in helpers.ts treats any
non-empty `#messages-json-content` as a started run and causes false positives
when fixtures are preloaded; update the check to compare the current messages
array length against the prior message count captured before clicking so we only
return true when a new run actually produced additional messages. Concretely: in
runTest() capture the preClickCount by parsing
document.getElementById('messages-json-content')?.textContent (default []), then
call page.evaluate with that preClickCount and inside the evaluated function
parse the messages once, return true if metadata.getAttribute('data-is-loading')
=== 'true' OR (Array.isArray(messages) && messages.length > preClickCount);
reference page.evaluate, '`#messages-json-content`', and the runTest() caller to
locate and implement this change.
---
Outside diff comments:
In `@packages/typescript/ai/src/activities/chat/middleware/types.ts`:
- Around line 349-387: The onStructuredOutputConfig hook currently types its
context as ChatMiddlewareContext (losing the generic TContext); update the
signature on ChatMiddleware<TContext> so onStructuredOutputConfig receives ctx:
ChatMiddlewareContext<TContext> (and keep the existing
StructuredOutputMiddlewareConfig type for the second parameter) so the generic
runtime context is preserved through this hook; locate the ChatMiddleware
interface and change the onStructuredOutputConfig parameter type accordingly
(referencing ChatMiddleware, onStructuredOutputConfig, ChatMiddlewareContext,
and StructuredOutputMiddlewareConfig).
---
Nitpick comments:
In `@packages/typescript/ai/tests/middleware-context.test.ts`:
- Line 47: The test currently uses structural equality
(expect(seen).toEqual([context, context])) which allows cloned objects to pass;
change it to assert reference identity by replacing that assertion with identity
checks such as expect(seen[0]).toBe(context) and expect(seen[1]).toBe(context)
so both captured entries are the exact same runtime context instance.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: 6bb95160-469b-4912-9470-f4089a8b533b
📒 Files selected for processing (60)
docs/advanced/middleware.mddocs/advanced/runtime-context.mddocs/api/ai-client.mddocs/api/ai-preact.mddocs/api/ai-react.mddocs/api/ai-solid.mddocs/api/ai-svelte.mddocs/api/ai-vue.mddocs/api/ai.mddocs/config.jsondocs/migration/ag-ui-compliance.mddocs/migration/migration-from-vercel-ai.mddocs/tools/client-tools.mddocs/tools/server-tools.mdexamples/ts-code-mode-web/src/lib/execute-prompt.tsexamples/ts-code-mode-web/src/lib/structured-output.tsexamples/ts-react-chat/src/components/Header.tsxexamples/ts-react-chat/src/lib/guitar-tools.tsexamples/ts-react-chat/src/routeTree.gen.tsexamples/ts-react-chat/src/routes/api.tanchat.tsexamples/ts-react-chat/src/routes/example.runtime-context.tsxpackages/typescript/ai-client/src/chat-client.tspackages/typescript/ai-client/src/index.tspackages/typescript/ai-client/src/types.tspackages/typescript/ai-client/tests/chat-client-context.test.tspackages/typescript/ai-client/tests/tool-types.test.tspackages/typescript/ai-code-mode/src/types.tspackages/typescript/ai-code-mode/tests/create-code-mode-tool.test.tspackages/typescript/ai-preact/src/types.tspackages/typescript/ai-preact/src/use-chat.tspackages/typescript/ai-react/src/types.tspackages/typescript/ai-react/src/use-chat.tspackages/typescript/ai-react/tests/use-chat-types.test.tspackages/typescript/ai-solid/src/types.tspackages/typescript/ai-solid/src/use-chat.tspackages/typescript/ai-svelte/src/create-chat.svelte.tspackages/typescript/ai-svelte/src/types.tspackages/typescript/ai-svelte/tests/create-chat-types.test.tspackages/typescript/ai-vue/src/types.tspackages/typescript/ai-vue/src/use-chat.tspackages/typescript/ai/src/activities/chat/index.tspackages/typescript/ai/src/activities/chat/middleware/compose.tspackages/typescript/ai/src/activities/chat/middleware/types.tspackages/typescript/ai/src/activities/chat/tools/tool-calls.tspackages/typescript/ai/src/activities/chat/tools/tool-definition.tspackages/typescript/ai/src/types.tspackages/typescript/ai/src/utilities/chat-params.tspackages/typescript/ai/tests/middleware-context.test.tspackages/typescript/ai/tests/tool-call-manager-context.test.tspackages/typescript/ai/tests/tool-calls-context.test.tspackages/typescript/ai/tests/tool-context.test.tspackages/typescript/ai/tests/type-check.test.tstesting/e2e/fixtures/tools-test/client-context.jsontesting/e2e/fixtures/tools-test/client-server-context.jsontesting/e2e/fixtures/tools-test/server-context.jsontesting/e2e/src/lib/tools-test-tools.tstesting/e2e/src/routes/api.tools-test.tstesting/e2e/src/routes/tools-test.tsxtesting/e2e/tests/tools-test/helpers.tstesting/e2e/tests/tools-test/runtime-context.spec.ts
✅ Files skipped from review due to trivial changes (14)
- testing/e2e/fixtures/tools-test/client-server-context.json
- docs/tools/server-tools.md
- testing/e2e/tests/tools-test/runtime-context.spec.ts
- docs/migration/ag-ui-compliance.md
- packages/typescript/ai-code-mode/tests/create-code-mode-tool.test.ts
- docs/api/ai-vue.md
- docs/api/ai-react.md
- docs/api/ai-solid.md
- examples/ts-code-mode-web/src/lib/structured-output.ts
- docs/migration/migration-from-vercel-ai.md
- docs/advanced/middleware.md
- docs/api/ai-preact.md
- docs/tools/client-tools.md
- examples/ts-react-chat/src/routeTree.gen.ts
Comment on lines
+94
to
+107
| const started = await page.evaluate(() => { | ||
| const metadata = document.getElementById('test-metadata') | ||
| if (metadata?.getAttribute('data-is-loading') === 'true') { | ||
| return true | ||
| } | ||
|
|
||
| const text = | ||
| document.getElementById('messages-json-content')?.textContent || '[]' | ||
| try { | ||
| return Array.isArray(JSON.parse(text)) && JSON.parse(text).length > 0 | ||
| } catch { | ||
| return false | ||
| } | ||
| }) |
Contributor
There was a problem hiding this comment.
Prevent false-positive test start detection with preloaded history.
Line 103 treats any non-empty #messages-json-content as “started”. With preloaded fixtures, messages can already be non-empty before clicking, so runTest() can return before a new run actually begins.
Suggested fix
export async function runTest(page: Page): Promise<void> {
+ const initialMessageCount = await page.evaluate(() => {
+ const text =
+ document.getElementById('messages-json-content')?.textContent || '[]'
+ try {
+ const parsed = JSON.parse(text)
+ return Array.isArray(parsed) ? parsed.length : 0
+ } catch {
+ return 0
+ }
+ })
+
for (let attempt = 0; attempt < 5; attempt++) {
await page.click('`#run-test-button`')
await page.waitForTimeout(300)
- const started = await page.evaluate(() => {
+ const started = await page.evaluate((baselineCount: number) => {
const metadata = document.getElementById('test-metadata')
if (metadata?.getAttribute('data-is-loading') === 'true') {
return true
}
const text =
document.getElementById('messages-json-content')?.textContent || '[]'
try {
- return Array.isArray(JSON.parse(text)) && JSON.parse(text).length > 0
+ const parsed = JSON.parse(text)
+ return Array.isArray(parsed) && parsed.length > baselineCount
} catch {
return false
}
- })
+ }, initialMessageCount)
if (started) {
return
}
}🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@testing/e2e/tests/tools-test/helpers.ts` around lines 94 - 107, The current
page.evaluate in helpers.ts treats any non-empty `#messages-json-content` as a
started run and causes false positives when fixtures are preloaded; update the
check to compare the current messages array length against the prior message
count captured before clicking so we only return true when a new run actually
produced additional messages. Concretely: in runTest() capture the preClickCount
by parsing document.getElementById('messages-json-content')?.textContent
(default []), then call page.evaluate with that preClickCount and inside the
evaluated function parse the messages once, return true if
metadata.getAttribute('data-is-loading') === 'true' OR (Array.isArray(messages)
&& messages.length > preClickCount); reference page.evaluate,
'`#messages-json-content`', and the runTest() caller to locate and implement this
change.
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.
Summary
useChatwrappers without breaking untyped middleware/tools.chat()and client-local context throughChatClientso tool and middleware implementations can access typed runtime data.ts-react-chatruntime context route.Test Plan
git diff --cached --checkpnpm --filter @tanstack/ai-event-client buildpnpm --filter @tanstack/ai test:typespnpm --filter @tanstack/ai buildpnpm --filter @tanstack/ai-client test:typespnpm --filter @tanstack/ai test:lib -- run tests/tool-context.test.ts tests/tool-calls-context.test.ts tests/tool-call-manager-context.test.ts tests/middleware-context.test.ts tests/type-check.test.tspnpm --filter @tanstack/ai-client test:lib -- run tests/chat-client-context.test.ts tests/tool-types.test.tspnpm --filter @tanstack/ai-client buildpnpm --filter @tanstack/ai-react test:typespnpm --filter @tanstack/ai-solid test:typespnpm --filter @tanstack/ai-vue test:typespnpm --filter @tanstack/ai-svelte test:typespnpm --filter @tanstack/ai-preact test:typespnpm --filter @tanstack/ai-code-mode test:typespnpm --filter @tanstack/ai-react test:lib -- run tests/use-chat-types.test.tspnpm --filter @tanstack/ai-svelte test:lib -- run tests/create-chat-types.test.tspnpm --filter @tanstack/ai-utils buildpnpm --filter @tanstack/openai-base build@tanstack/ai-openai,@tanstack/ai-anthropic,@tanstack/ai-gemini,@tanstack/ai-grok,@tanstack/ai-groq,@tanstack/ai-elevenlabs,@tanstack/ai-ollama,@tanstack/ai-openrouterpnpm --filter @tanstack/ai-e2e test:e2e -- tests/tools-test/runtime-context.spec.tsNotes: Vite/svelte-check emitted the existing missing
.svelte-kit/tsconfig.jsonwarning forexamples/ts-svelte-chat; the commands above exited successfully where listed.Summary by CodeRabbit
New Features
Documentation
Examples
Tests