Skip to content

Commit f500fc1

Browse files
committed
Drop a stale line-number reference in the callbacks doc
The import reshuffle in the callbacks tutorial moved `mode="legacy"` off line 17, so the admonition pointing at "line 17" now named the wrong line. Refer to the argument by where it lives (the `Client(...)` call) instead of by line number, so it can't drift again. No-Verification-Needed: doc-prose-only change
1 parent 262c17b commit f500fc1

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

docs/client/callbacks.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -55,7 +55,7 @@ result.content # [TextContent(type='text', text='Card issued to Ada Lovelace.')
5555
One `tools/call` from you, one `elicitation/create` back from the server, answered by your function, all inside a single tool call.
5656

5757
!!! info
58-
`mode="legacy"` on line 17 is doing real work. By default `Client(...)` negotiates the modern
58+
`mode="legacy"` on the `Client(...)` call is doing real work. By default `Client(...)` negotiates the modern
5959
protocol path, and that path has no back-channel for server-to-client requests: `ctx.elicit`
6060
fails before your callback ever runs. The transport doesn't decide that; the negotiated
6161
protocol does, in-memory and over a URL alike. Pin `mode="legacy"` whenever your client has

0 commit comments

Comments
 (0)