Update openai-fetch and handle refusal responses
#51
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
This commit updates the `openai-fetch` dependency to version 3.3.1. It also introduces handling for message refusals by throwing a `RefusalError` when a refusal is returned. This includes changes in `chat.ts`, test enhancements, and updates to message types and checks.
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
transitive-bullshit
approved these changes
Oct 13, 2024
|
haha you just beat me @transitive-bullshit. i opened #52, which does a whole bunch more than just this, but i decided to not throw errors and instead export a convenient guard function. it felt like too much of a slippery slope throwing because it means that the |
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.
openai-fetchto 3.3.1 and handle refusalsThis allows us to keep the message types stricter and avoid having to continually check for refusals by parsing all responses from the API and throwing a
RefusalErrorif the model sends a message with a refusal.