fix(provider): point aggregator setup_urls to fork README (#80)#182
Open
quangdang46 wants to merge 1 commit into
Open
fix(provider): point aggregator setup_urls to fork README (#80)#182quangdang46 wants to merge 1 commit into
quangdang46 wants to merge 1 commit into
Conversation
Eleven OpenAI-compatible aggregator profiles in crates/jcode-provider-metadata/src/catalog.rs (opencode-zen, opencode-go, 302ai, baseten, cortecs, firmware, hugging-face, moonshot-ai, nebius-token-factory, scaleway, stackit) shipped `setup_url` values pointing at `https://opencode.ai/docs/providers#<id>`. Those URLs 404 from jcode's perspective — opencode.ai's docs site does not host jcode-specific provider setup pages, so users hitting the "setup" link in the login UI got a useless landing. Replace all eleven with `https://github.com/quangdang46/jcode#oauth-and-providers`, which is the fork's README section that actually documents how to configure these providers (including `jcode login --provider <id>` commands and per-provider env vars). Strengthen `auth_issue_profile_metadata_matches_direct_provider_endpoints` in src/provider_catalog_tests.rs to assert no aggregator setup_url still references `opencode.ai/docs`, plus pin the new opencode / opencode-go URLs explicitly. Ports the intent of upstream PR 1jehuang#91 (which uses the upstream README anchor); URLs adjusted to point at this fork's README instead. Closes #80
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
1 participant
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
Eleven OpenAI-compatible aggregator profiles in
crates/jcode-provider-metadata/src/catalog.rs(opencode-zen, opencode-go, 302ai, baseten, cortecs, firmware, hugging-face, moonshot-ai, nebius-token-factory, scaleway, stackit) shippedsetup_urlvalues pointing athttps://opencode.ai/docs/providers#<id>. Those URLs 404 from jcode's perspective — opencode.ai's docs site does not host jcode-specific provider setup pages, so users hitting the "setup" link in the login UI got a useless landing.This addresses issue #80: #80
Changes
opencode.ai/docs/providers#<id>URLs withhttps://github.com/quangdang46/jcode#oauth-and-providers(the fork README section that actually documents these providers). Verified withgrep -c 'opencode.ai/docs/providers' catalog.rs == 0.auth_issue_profile_metadata_matches_direct_provider_endpointsto:opencode.ai/docs.OPENCODE_PROFILE.setup_urlandOPENCODE_GO_PROFILE.setup_urlto the new value explicitly.Tests
Notes / scope deviation from upstream
https://github.com/1jehuang/jcode#openai-compatible-providersas the replacement URL and also bumpsOPENCODE_GO_PROFILE.default_modelfrom GLM-4.5 to GLM-4.9. This fork already uses different defaults (minimax-m2.7for opencode-zen,kimi-k2.5for opencode-go), so the model bump is not applicable. Replacement URL points to this fork's README so the link works in the user's actual login UI.#oauth-and-providersanchor because it's a stable, top-level README section that exists today. If you'd rather use a deeper anchor or move the docs to OAUTH.md, happy to follow up.