)) .json(body) .headers(build_headers(api_token, ide)?) .send() .await .map_err(internal_error)?; // ... }">

async fn request_completion(
    http_client: &reqwest::Client,
    ide: Ide,
    model: &str,
    request_params: RequestParams,
    api_token: Option<&String>,
    prompt: String,
    inputs_key: String,
    request_options: HashMap<String, String>,
) -> Result<Vec<Generation>> {
    let mut body = HashMap::new();
    body.extend(request_options);
    body.insert(inputs_key, prompt);
    body.insert("parameters", request_params.into());

    let res = http_client
        .post(build_url(model))
        .json(body)
        .headers(build_headers(api_token, ide)?)
        .send()
        .await
        .map_err(internal_error)?;

    // ...
}

Just an example, but we could add inputs_key and request_options to CompletionParams. To get this working for ollama a user could give inputs_key as "prompt" and request_options as { model: "ollama:7b-code" }.

Also as an aside, I don't get why we wouldn't be passing the params as a whole to the request_completion call? Would this be bad practise in Rust?

// Before
let result = request_completion(
    http_client,
    params.ide,
    params.model,
    params.request_params,
    params.api_token.as_ref(),
    prompt,
)
// After
let result = request_completion(
    http_client,
    params,
    prompt,
)

feat: add support for ollama #17

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions