fix(oobe): 修复OOBE版本步骤的路由逻辑避免死循环

更新正式版的下一步路由为oobe/finish而非agreement,防止形成agreement → legal → welcome → version → agreement的死循环;同时补充详细的前置流程注释说明步骤顺序。
This commit is contained in:
2026-08-31 03:31:41 +08:00
parent 403a861b89
commit 512e4ae3d7
3 changed files with 6 additions and 3 deletions
+1
View File
@@ -34,3 +34,4 @@ electron-dist/
build/ build/
dsh-usage/usage-records.json dsh-usage/usage-records.json
Koring.yml Koring.yml
dsh-usage/usage-records.json
File diff suppressed because one or more lines are too long
+4 -2
View File
@@ -9,8 +9,10 @@ export function OobeVersion() {
const isTestBuild = BUILD_MODE === "dev" || BUILD_MODE === "beta"; const isTestBuild = BUILD_MODE === "dev" || BUILD_MODE === "beta";
// 临时跳过 Koring 账户登录环节:正式版也直接进入用户协议 // 到达本页前已依次经过 协议(agreement) → 法律(legal) → 欢迎(welcome)
const nextRoute = isTestBuild ? "oobe/beta-test" : "oobe/agreement"; // 因此正式版下一步直接结束;测试版需先同意 Beta 测试协议。
// (不要跳回 agreement——那会形成 agreement → legal → welcome → version → agreement 死循环)
const nextRoute = isTestBuild ? "oobe/beta-test" : "oobe/finish";
return ( return (
<OobeLayout> <OobeLayout>