Add possibility to use api_key per chat invocation. #46
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
|
Your use case makes sense and it's a clean solution. Thanks! ❤️💛💙💜 |
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.
In this PR I'm suggesting an addition of api_key passing directly through the Chat interface. This is done to allow users of the library to dynamically pass api_key based on who is using the chat.
My personal use case is as following:
I give my users possibility to pass their own OpenAI API_KEY through interface. Because of that I can't retrieve it from config. I have to inject it during the call.
In case I''ve missed anything in the PR I'm happy to improve it!
Thanks!