refactor: remove REST endpoint from SDK and admin config#1529
Conversation
Remove legacy REST endpoint field from FrontierClientOptions as all network calls now go through connect-rpc. Also remove duplicate FrontierClientOptions, FrontierProviderProps and InitialState from sdk/src/types.ts. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Remove NEXT_PUBLIC_FRONTIER_URL and use only connect endpoint (NEXT_PUBLIC_FRONTIER_CONNECT_URL) for all RPC calls. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (5)
💤 Files with no reviewable changes (4)
📝 WalkthroughSummary by CodeRabbit
WalkthroughThe pull request removes the legacy Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~12 minutes Possibly related PRs
Suggested reviewers
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Coverage Report for CI Build 24231766259Coverage remained the same at 41.328%Details
Uncovered ChangesNo uncovered changes found. Coverage RegressionsNo coverage regressions found. Coverage Stats💛 - Coveralls |

Summary
endpointfromFrontierClientOptionsin SDK (bothshared/types.tsand legacysrc/types.ts)NEXT_PUBLIC_FRONTIER_URLfrom admin config andturbo.jsonconnectEndpoint(NEXT_PUBLIC_FRONTIER_CONNECT_URL)FrontierClientOptions,FrontierProviderProps,InitialStatefromsdk/src/types.tsTest plan
🤖 Generated with Claude Code