Added BaseOptions to ChatOpenAI #787
Merged
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
HenryHengZJ
approved these changes
Aug 17, 2023
hemati
pushed a commit
to hemati/Flowise
that referenced
this pull request
Dec 27, 2023
…eOption Added BaseOptions to ChatOpenAI
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.
Motivation:
Had the need to pass Helicone's API key but there was no way to pass the BaseOptions needed on the documentation.
Used a very similar code to pupeteer's node metadata input. Just added a try..catch, in case something is wrong with the JSON, so the user can identify where it is coming from.
BaseOptions on ChatOpenAI node
Example call to Helicone
Custom properties working as well, so any use you may have for BaseOptions now are possible