[WIP] feat(history): Allow history to be more flexible to new kinds of user inputs #9115
+777
−109
Conversation
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
isaacbmiller
force-pushed
the
isaac/dspy-history-refactor2
branch
from
55151bc to
6cb1249
Compare
- Improved docstring for the History class to clarify its purpose and usage. - Added examples for different message modes (raw, demo, signature, flat) with explicit mode specification. - Updated tests to ensure correct mode detection, including new cases for tool call IDs and names. - Refactored tests to use parameterized cases for explicit mode settings. - Allowed empty messages list in History, defaulting to flat mode. - Removed deprecated factory methods in favor of direct message input in docs.
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.
📝 Changes Description
Refactors both dspy.History.
Goal
Multi turn chat has been a weaker part of the DSPy dx. It is not clear how you should maintain history, nor particularly easy to do so. These PRs should allow you to build multi turn, (optionally tool use) chatbots more easily.
This PR is the start of efforts to alleviate the concerns.
Overview
History
DSPy.History used to be set to only a single input type.
All inputs and outputs needed to match the current signature that is being used otherwise each step would be filtered to match those fields. This was done to guarantee that we could separate into proper user/assistant pairs. We relax that constraint and give the user more flexibility on how to collect and display messages.
History now has 4 possible modes that it can handle:
signature (the old default) - will filter strictly to the current signature
demos - has input/output fields labeled via a nested dict with: `{"input_fields": {"k":"v"}, "output_fields":{"k":"v"}}, but does not require them to match a signature. This still allows you to get user/assistant splitting.
flat - a dict of kv pairs - all messages go into the user side
raw - uses user/assistant messages
Next PRs: