Preserve Non-AI Messages in Message Operations #27
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
When updating tool names, the message operation was dropping non-AI messages (like SystemMessage, HumanMessage, and ToolMessage). This PR fixes the issue by ensuring all message types are preserved during message operations, maintaining the complete conversation context and history.
Changes
Testing
Added test cases that verify:
Impact
This change ensures that conversation context is maintained correctly when updating tool names, which is particularly important for maintaining coherent dialogue history in the trustcall system.