Chore/return model in response

[narengogi]

Title:

• Brief Description of Changes

Description:

🔄 What Changed

• The Pull Request introduces changes to return the model in responses for various providers, including Bedrock, Anthropic, and others. It modifies the response handling functions to include the model in the response structure.
• Several functions have been updated to accept a new parameter gatewayRequest, which contains the model information.

🔍 Impact of the Change

• This change enhances the response structure by including the model used for generating the response, which can be beneficial for debugging and tracking the model's performance.
• It ensures that all providers return consistent information regarding the model used, improving the overall API usability.

📁 Total Files Changed

• 20 files were modified in this Pull Request.

🧪 Test Added

• No new tests were added in this Pull Request. It is recommended to add unit tests to verify the new functionality of returning the model in responses.

🔒 Security Vulnerabilities

• No security vulnerabilities were detected in this Pull Request.

[VisargD]

Openrouter now sends model in the response itself. We can use that directly.

[VisargD]

TogetherAI now sends model in the response itself. We can use it directly.

[b4s36t4]

/matter summary

[matter-code-review]

I'm generating a summary for this PR. I'll post it shortly.

[matter-code-review]

Chore/return model in response

🔄 What Changed

• The responseHandler function in responseHandlers.ts was modified to include a new parameter gatewayRequest.
• The readAWSStream and readStream functions in streamHandler.ts were updated to accept the gatewayRequest parameter.
• Multiple response transformation functions across various providers (e.g., AI21, Bedrock, Cohere) were updated to include the gatewayRequest parameter, allowing for better handling of model information.

🔍 Impact of the Change

• This change enhances the flexibility of the response handling by allowing the model information to be passed through the gatewayRequest parameter, which can improve the accuracy of responses generated by different AI providers.

📁 Total Files Changed

• 12 files were modified in this pull request, with a total of 380 lines changed (additions and deletions combined).

🧪 Test Added

• No new tests were added in this pull request. It is recommended to add unit tests to verify the behavior of the modified functions, especially focusing on the handling of the new gatewayRequest parameter.

🔒 Security Vulnerabilities

• No security vulnerabilities were detected in this pull request.

[b4s36t4]

/matter review

[matter-code-review]

I'm reviewing this PR now. I'll provide feedback shortly.

[matter-code-review]

The changes look good overall, but please consider adding unit tests to ensure the new functionality is covered.

[b4s36t4]

/matter explain

[matter-code-review]

This Pull Request introduces several modifications primarily focused on enhancing the response handling for various AI providers by including the model in the responses. The changes span multiple files and involve both non-streaming and streaming response handlers.

1. Response Handlers Update: The responseHandlers.ts file has been modified to include a new parameter gatewayRequest in the responseHandler function. This allows the function to access the model information from the request, which is crucial for generating accurate responses.

2. Stream Handlers Update: The streamHandler.ts file has also been updated to include the gatewayRequest parameter in several functions, such as readAWSStream and readStream. This change ensures that the model information is consistently passed through the streaming process, allowing for more accurate response generation.

3. Provider-Specific Changes: Each provider's response transformation functions (e.g., AI21ChatCompleteResponseTransform, BedrockChatCompleteResponseTransform, etc.) have been updated to accept the gatewayRequest parameter. This allows the model to be included in the response object, which is essential for tracking which model was used for generating the response.

4. Error Handling: The error response transformations have also been updated to include the model in the error responses, ensuring that even in failure cases, the model information is available for debugging and logging purposes.

5. New Dependencies: The Params type has been imported in several files to ensure that the gatewayRequest parameter is correctly typed, enhancing type safety and reducing potential runtime errors.

6. Testing: While the PR does not explicitly mention new tests, the extensive changes to the response handling logic imply that existing tests may need to be updated to account for the new parameters and ensure that the model information is correctly handled in both success and error scenarios.

Overall, this PR significantly enhances the response handling capabilities of the application by ensuring that the model information is consistently included across various AI providers, improving the traceability and accuracy of responses.