Skip to content

feat: request modelling for every single provider #496

@joshua-mo-143

Description

@joshua-mo-143
  • I have looked for existing issues (including closed) about this

Feature Request

Sub-ticket of #381.

There's a lot more work ahead of this ticket, but we have to start somewhere. As completion models are the most used model type in this library, this makes the most sense.

Motivation

Advancing #381

Proposal

In accordance with the overarching epic, we should probably model requests for each provider so that we can add IDs to each request (whether it's an agent ID or a conversation ID).

This work primarily involves adding a breaking change to the CompletionModel trait so that we have an associated Request type - then all we need to do is impl From<CompletionRequest> for each request made.

Alternatives

None

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions