Feature/proxy requests #129
Open
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.
This PR adds a more generic approach to proxying requests to the OpenAI API through channels other than direct
URLSessionfrom the app.For example, if you used a particular networking library in the app you could conform your networking client to
OpenAIRequestHandlerand make the requests yourselves. Or if you were using firebase callable functions as your proxy, or any other kind of "serverless" approach that has its own SDK you could use that instead.I have made a concerted effort to make this entirely backwards compatible, this has been done by typealiasing
Config = URLSessionRequestHandlerand adding a secondary initialiser to theOpenAISwiftclass which takes an instance of the protocolOpenAIRequestHandlerso that users who are either using:or
do not have any breaking changes, but users who want to implement their own request handling can use:
I have tested this with our own integration of the OpenAISwift library and all existing functionality works the same. Note: this also includes the fix for 400 error due to adding
Identifiableprotocol toChatMessageas seen here: #122