fix(events): rename error event data key from message to text#63
Merged
Conversation
Normalizes the ERROR event schema — all events that carry a human-readable string payload now use the `text` key consistently.
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.
Description
The
ERRORevent emitted byEventPublisheruseddata["message"]as the key for the exception string, while every other event that carries a human-readable string payload usesdata["text"](TOKEN,REASONING,AGENT_COMPLETE). Renames the key totextfor consistency.Related Issues
N/A
Type of Change
YAML / API Impact
No schema or Python API changes. Breaking only for consumers reading
event.data["message"]onERRORevents — they must switch toevent.data["text"]. All other event shapes are unchanged.Testing
uv run just check(lint + type check)uv run just testfor overall testingexamples/still workChecklist