jackMort/ChatGPT.nvim

Make it compatible with deepinfra

Open

#438 opened on May 16, 2024

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Lua (4,005 stars) (323 forks)batch import
enhancementgood first issue

Description

I am trying to use thsi plugin with deepinfra which offers llama3b-70b on the cheap and a openAI compatible api, how ever its api endpoints has "openai" in the middle like this

https://api.deepinfra.com/v1/openai/chat/completions

And current code hard-coded to add /v1/chat/completions path to api base address, and this makes it not able to make api calls correctly to deepinfra api endpoint.

Would it be possible to make "v1" part of api base url? I know this is a breaking change, but it does not make a lot of sense to hard-code an api version in request paths, right?

Contributor guide

Tech stack
None
Domain
api
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
familiarity with HTTP API requestsbasic Lua programming
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
85
Research direction
Investigate the current code to find where `/v1/chat/completions` is hardcoded. Likely in a function that constructs the API endpoint URL. Determine the best approach to allow users to customize the path or make it part of the base URL. Consider adding a configuration option for the API base URL that includes the version path. Ensure backward compatibility by defaulting to the existing behavior.