Replies: 1 comment
-
Was easy enough it turns out
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Checked other resources
Commit to Help
Example Code
Description
I have been at this for about five hours. It seems fairly basic to me, but I cannot work it out!
TLDR; how do I indicate to langserve the requirement for a particular configurable property on my
with_message_history
runnable?Currently, the reported FastAPI schema for my chain looks like this:
I am trying to introduce a
personality_name
property that is used to create a prompt, rather than have a fixed prompt.In my code above, I have no idea how to indicate to langserve that there is now a
prompt_name
configurable, so that the API would now look like this:I have tried at least a half dozen ways to enforce this, but none of them have worked.
history_factory_config
looked promising, but then this passes all of those properties to the history retriever, which has no interest in them and I believe should not be modified. I suppose I want a sort of "passthrough" behaviour.I did encounter this explanation of configuring runnables, but the warning at the top made me hesitate, since I do not believe this to be an advanced requirement.
So I thought I would check with the community before implementing my own Runnable.
System Info
System Information
Package Information
Other Dependencies
Beta Was this translation helpful? Give feedback.
All reactions