Support for custom endpoints #84
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Thank you! Will review and merge. |
|
Thanks! Hope I am not being a burden - let me know if you need anything. |
|
The conflicts, I think you not pulled latest changes before working on it 😆 Also could you please add the documentation about it in README.md? |
|
Also would be nice if you fix the conflicts xD Then i'll add tests and will make this ready to merge. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What:
Support for custom endpoints.
Why:
Right now you can create custom API models, but it would be useful to have support for custom endpoints that use familiar API structures.
Examples include: Azure OpenAI, Vertex Studio, Ollama. There are all services that can create endpoints compatible with the OpenAI or Gemini API clients (or REST in this case). They are drop-in replacements that work simply by changing the endpoint URL, so implementing them through the customCopilot option would be needlessly hard.
How:
I changed up the
createProviderEndpointmethod to support custom endpoints, and allowed for the user to input a custom endpoint in the Copilot class.Checklist:
Probably not ready to merge. It may need tests, but I am unfamiliar with Vitest (I use Mocha).
I am happy to add documentation and fix bugs if needed though.
Thanks!