Fix duplicate artifact rendering in chat stream #330
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
Fixes a bug where artifacts were being rendered twice in the chat interface when an event contained both content (text or function calls) and an artifact delta.
Fixes
#325
google/adk-python#4036
What it does
Fixes Artifact Duplication: Updates storeMessage in ChatComponent to only process
artifactDeltawhen the method is invoked for action processing (specifically whenpartis null). This ensures that calls to storeMessage for handling content (liketextorfunctionCall) do not redundantly re-trigger artifact rendering.Regression Testing: Adds comprehensive test cases to chat.component.spec.ts to verify that duplication is prevented while ensuring artifacts are still correctly rendered for text-only responses.
Features Demonstrated
Testing Plan
npm run test(orng test) and verify all 441 tests pass.should not duplicate artifact message when event has both content and artifact deltashould render artifact for text-only responseChecklist