support for custom input types in DSPy signatures #8210
Closed
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
arnavsinghvi11
changed the title
|
Per our discussions offline, moving away from special case handling for DSPy type is agreed on, but we need to simplify this implementation for scalability. I will push a few commits this week. |
Merged
Merged
|
Closed via #8217 |
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.
adds support for defining custom input types in signatures with unified formatting of input messages in BaseAdapter
also compatible with existing types (dspy.Image, dspy.History), refactors some hard-coded functions of dspy.Image to use the CustomType-BaseAdapter integration