test(cli): cover login --token defaulting to hosted relayfile - #401
test(cli): cover login --token defaulting to hosted relayfile#401khaliqgant wants to merge 1 commit into
Conversation
Verified — no production code change needed — that the CLI already defaults to https://file.agentrelay.com. Traced defaultServerURL through runLogin, loginWithAPIKey, newAPIClient, and resolveServer; no Go code retains the stale https://api.relayfile.dev default. Adds a real regression test asserting login --token with no --server issues its health check against, and persists, the hosted endpoint. Closes #328. Verified: - go build ./... - go test ./cmd/relayfile-cli/... -run TestLoginWithTokenDefaultsToHostedRelayfile -v -count=1 - go test ./cmd/relayfile-cli/... -count=1 (full package suite)
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
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 |
Relayfile Eval ReviewRun: Passed: 4 | Needs human: 0 | Reviewable: 0 | Missing output: 0 | Failed: 0 | Skipped: 0 Human Review CasesNo reviewable human-review cases captured Relayfile output. |
1 participant
Closes #328.
Verified — no production code change needed — that the CLI already defaults to `https://file.agentrelay.com\`. Traced `defaultServerURL` through `runLogin`, `loginWithAPIKey`, `newAPIClient`, and `resolveServer`; no Go code retains the stale `https://api.relayfile.dev\` default. Adds a real regression test asserting `login --token` with no `--server` issues its health check against, and persists, the hosted endpoint.
Test plan