Improve literal format adherence in ChatAdapter, JSONAdapter #1955
Conversation
This file contains 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
dbczumar
changed the title
Signed-off-by: dbczumar <corey.zumar@databricks.com>
dbczumar
commented
Jan 11, 2025
|
|
||
| if origin is Literal: | ||
| args_str = ", ".join( | ||
| _quoted_string_for_literal_type_annotation(a) if isinstance(a, str) else get_annotation_name(a) |
There was a problem hiding this comment.
@okhat This is slightly trickier than using repr(), since repr() inserts undesired backslashes that are likely to confuse an LM. I think the approach proposed in the PR should hopefully reduce LM confusion with strings containing quotes
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.
Improve literal format adherence in ChatAdapter
Testing
Confirmed that existing reliability tests pass with GPT-4o and Llama3.1 70B Instruct