Allow customization of invalid json reprompt #1204
Merged
+13
−3
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
edeandrea
force-pushed
the
enhance-json-guardrail
branch
from
c707f15 to
b03f26d
Compare
Status for workflow
|
cescoffier
approved these changes
Jan 9, 2025
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.
Allow customization of invalid json reprompt.
In some implementations I'm finding that the message
Make sure you return a valid JSON object following the specified formatis too generic. On specific implementations I'd like to include the json format in the reprompt message.This change allows implementors to override the message, or change the implementation of the reprompt altogether (maybe an implementor just wants to fail?).
This change is 100% backwards compatible with current behavior but allows implementors to customize.