Feat plan usage - #978
Merged
Merged
Conversation
桌面端连上 MonkeyCode 后看不到自己的会员权益,只能去移动端「我的」页看。 设置 → 账号的 MonkeyCode 卡里补上同一套信息,口径与移动端对齐。 壳侧 mc_usage 并发取回钱包/订阅/签到态/邀请四路,单路失败按 null 降级 (私有化部署只有订阅端点,其余 404,此时仍要能看到会员等级),全部失败 才报错。签到态取不到时给 null 而非 false,否则会误催已签到的用户。 mc_checkin 复用账密登录那套 MonkeyCode 域 PoW 验证码,凭证不出内核。 base_url 随权益一并回传:邀请链接和相对头像地址都以它为解析基准,UI 自己 按主机名拼 https:// 会在自建 http/带端口部署上拼错。 权益只在设置页可见,故由设置页挂载时自取,没有挂进 App 那条 30 秒云端 轮询——那等于为一块看不见的面板长期空跑四个请求。状态放 SettingsView 而非账号卡内:同步会把分区切到模型页,卡会随之卸载。 奖励数额(+100/+5000)服务端不下发,与移动端一样两端各自硬编码。
同步成功会当场把分区切到模型页(mergeSyncedModels),消息所在的账号卡随之 退出视野——"正在保存并重启内核…"在卡里根本来不及被看到,却会在用户下次 点回账号时以早已过期的状态出现(那会儿保存早结束了)。 自动保存这一路不再写进行时,消息只留事实;纯成功(既无待办也无附加说明) 的消息标记 transient,离开分区即作废。带待办(需手动保存)或附加说明 (跳过名单、内核诊断、新建密钥)的留着——那些话在用户切回来时依然成立; 失败消息也不受影响:出错不切分区,用户就在账号页看着。 判据抽成 settingsConfig.syncResultTail 由两条同步流水线共用并单测钉住。 顺带修正会员模型那条的兜底文案:保存在途(blocked 为空但没直接存)此前 误报"表单有未保存的修改",与百智云一致改为"已切到模型页,核对后保存"。
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.
No description provided.