Move provider api into separate library to make it easier to maintain and sync with something like cline #2669
Conversation
|
dosubot
bot
added
the
size:XXL
|
Generated with ❤️ by ellipsis.dev |
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
| const isAzureAiInference = this._isAzureAiInference(modelUrl) | ||
| const urlHost = this._getUrlHost(modelUrl) | ||
| const deepseekReasoner = modelId.includes("deepseek-reasoner") || enabledR1Format | ||
| const ark = modelUrl.includes(".volces.com") |
Check failure
Code scanning / CodeQL
Incomplete URL substring sanitization High
|
This pull request is quite large, with 260 files changed, 40,510 lines added, and 7,128 lines removed. It includes various changes such as new features, refactoring, and tests across multiple modules and files. To make it easier to review and maintain, consider splitting the changes into smaller, more focused pull requests. Here are some suggestions:
By splitting the pull request, it will be easier to review each set of changes independently and ensure that each part is thoroughly tested and integrated. |
RooCodeInc#2669) Bumps the npm_and_yarn group in /webview-ui with 1 update: [vite](https://github.com/vitejs/vite/tree/HEAD/packages/vite). Updates `vite` from 6.2.4 to 6.2.5 - [Release notes](https://github.com/vitejs/vite/releases) - [Changelog](https://github.com/vitejs/vite/blob/v6.2.5/packages/vite/CHANGELOG.md) - [Commits](https://github.com/vitejs/vite/commits/v6.2.5/packages/vite) --- updated-dependencies: - dependency-name: vite dependency-version: 6.2.5 dependency-type: direct:development dependency-group: npm_and_yarn ... Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
1 participant
Context
Added api_library.md to document the available API providers and their usage within the Roo-Code project. This aims to improve developer onboarding and make it easier to understand and extend the API provider system.
Implementation
Created a new markdown file, api_library.md, at the project root.
Documented the structure, usage, and extension points for API providers.
Provided high-level explanations and examples to clarify how the provider system works.
No major refactoring was required; this is a documentation addition only.
Tradeoff: Focused on clarity and completeness for new contributors, but further details can be added as the provider system evolves.
Screenshots
How to Test
Open api_library.md in the project root.
Review the documentation for accuracy and completeness.
Confirm that the documented examples and explanations match the current implementation of API providers.
Get in Touch
I'm in the Roo Code Discord as prestongarrison. Feel free to reach out with any questions or feedback!