Skip to content

docs: correct the Python and Go event data model tip #2160

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
SteveSandersonMS merged 2 commits into from
Jul 30, 2026
+2 −2
Merged

docs: correct the Python and Go event data model tip #2160

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
c88bd4a
docs: correct the Python and Go event data model tip
examon Jul 30, 2026
ab0c274
docs: use 'for example' instead of 'e.g.' per style guide
examon Jul 30, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .github/instructions/docs-style.instructions.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -49,7 +49,7 @@ When a callout applies to a specific language, put the qualifier as bold text in

```markdown
> [!TIP]
> **(Python / Go)** These SDKs use a single `Data` class/struct with all fields optional.
> **(Python / Go)** These SDKs use separate, per-event data types.
```

## Lists
Expand Down
2 changes: 1 addition & 1 deletion docs/features/streaming-events.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -210,7 +210,7 @@ session.on(AssistantMessageDeltaEvent.class, event ->
</details>

> [!TIP]
> **(Python / Go)** These SDKs use a single `Data` class/struct with all possible fields as optional/nullable. Only the fields listed in the tables below are populated for each event type—the rest will be `None` / `nil`.
> **(Python / Go)** These SDKs use separate, per-event data types (for example, `AssistantMessageDeltaData`), so only the relevant fields exist on each type.
>
> [!TIP]
> **(.NET)** The .NET SDK uses separate, strongly-typed data classes per event (e.g., `AssistantMessageDeltaData`), so only the relevant fields exist on each type.
Expand Down
Loading