Repository navigation
feat(ui): three-level provider → plan → model listing form - #30
Merged
Merged
Conversation
Users mostly share their plan subscriptions (e.g. Aliyun Token Plan, Kimi Code) rather than pay-as-you-go keys, and different plans of the same provider may have different base URLs. Rework the listing form to select provider → plan → model, with a built-in catalog of known domestic plans (each provider has an "API(按量)" pay-as-you-go entry). Selecting a plan shows key-prefix / endpoint hints. The listing table now shows "provider · plan / model" (e.g. 智谱 · GLM Coding Plan / glm-5.2). Auto pricing by model is unchanged. Adds an aliyun-bailian model (qwen3-max) so the Aliyun plans have selectable models. Refs: rant 2026-08-17T10:51:24 (上架表单改为"厂商 → Plan → 模型")
3 tasks done
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
Rework the listing (上架) form from "provider → model" to a three-level cascade provider → Plan → model, with a built-in catalog of known domestic plans. Users mostly share their plan subscriptions (Aliyun Token Plan, Kimi Code, …) rather than pay-as-you-go keys, and different plans of the same provider can have different base URLs — so the listing selects the provider's Plan (where "API" means a pay-as-you-go key), then the models that plan supports.
Rant reference
Host instruction (rant
2026-08-17T10:51:24, 上架表单改为"厂商 → Plan → 模型"):Changes (ui/)
ui/js/data.js:PLANSarray — 12 plans across 6 providers (阿里云百炼 / 智谱 / 火山方舟 / Kimi 月之暗面 / MiniMax / DeepSeek), each provider including anapi-type "API(按量)" entry; fieldsid / provider / name / type(api|coding|token) / keyPrefix / notePROVIDER_LABELSmap for display namesaliyun-bailianmodel (qwen3-max) so the Aliyun plans have selectable modelsSHARINGSentries now carryprovider+planui/index.html: form gains a Plan select (#sf-plan) + hint line (#sf-plan-hint) between provider and model; listing table header → "厂商 · Plan / 模型"ui/js/app.js:showPlanHint()— shows key-prefix / endpoint note for the selected plan (e.g.sk-sp-,sk-cp-,/api/coding/v3)ui/README.md: synced sharing sectionVerification
node --check ui/js/app.js/ui/js/data.jspassapiplan (PASS), 12 plans totalcargo testpasses (1 passed)cargo fmt --checkpasses