Repository navigation
feat(settings): add API Route provider preset - #172
Merged
Merged
Conversation
Signed-off-by: dennyho0917 <dennyho0917@gmail.com>
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #172 +/- ##
=========================================
Coverage ? 68.36%
=========================================
Files ? 43
Lines ? 2437
Branches ? 599
=========================================
Hits ? 1666
Misses ? 595
Partials ? 176 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
This file contains hidden or 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
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.
Summary
Add API Route as a built-in preset in AI settings, following the small preset/changelog pattern from Requesty (#157) and Opper (#165).
I maintain API Route. This removes manual endpoint setup for its users while keeping the change limited to the existing settings flow. Two files changed; no dependencies or backend changes.
Verification
Rebased onto the latest master, including the newly merged Opper preset.
On Node 24:
Live gateway compatibility smoke checks: authenticated /models returned 60 IDs; a synthetic gpt-6.1-sol Chat Completions call returned SQLKIT_OK. This was an HTTP check, not a full Tauri end-to-end test. No database content or credentials are included in this PR.
Native Tauri launch and Rust/JDBC suites were not run locally for this frontend-only change.