-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(prompts): Prompt
interface should reference few-shot examples explicitly
#51
Comments
Prompt
interface should reference two-shot examples explicitelyPrompt
interface should reference two-shot examples explicitly
I find introducing name
|
Prompt
interface should reference two-shot examples explicitlyPrompt
interface should reference few-shot examples explicitly
@mhordynski We already use "message". Currently "prompt" means the static prompt template (that is always the same), and "message" means the actual rendered message that is send as part of the conversation. So for example, you can access both |
We decided to change Instead of |
To be honest, the current version with "message" seems quite intuitive to me, so personally I will be okay with leaving it as-is, but I can't deny your experience of getting confused by it. Some options:
|
It should be more clear that the ability to add additional messages to prompt instances is intended for adding few-shot messages, not keeping there the entire conversation history.
additional_messages
tofew_shots
add_user_message
andadd_assistant_message
methods with a singleadd_few_shot
method (which takes both question and answer)add_few_shot
appends the messages to a separate instance field, not the staticfew_shot
system_message
anduser_message
torendered_system_prompt
andrendered_user_prompt
chat
method so the conversation contains messages in the following order (and clearly document the order in the method docstring):rendered_system_prompt
few_shots
add_few_shot
rendered_user_prompt
The text was updated successfully, but these errors were encountered: