refactor(auth): 移除登录注册时的Zulip内存关联逻辑
范围: src/business/auth/ 涉及文件: - src/business/auth/login.service.ts - src/business/auth/register.service.ts 主要改进: - 移除登录时建立Zulip内存关联的代码 - 移除注册时建立Zulip内存关联的代码 - 改为在WebSocket连接时由Zulip客户端创建内存关联 - 优化了内存关联的时机,避免不必要的提前创建 技术说明: - 原逻辑在登录/注册时就建立内存关联,但用户可能不会立即使用Zulip - 新逻辑延迟到WebSocket连接时创建,更加合理和高效 - 减少了登录/注册流程的复杂度和耦合度
This commit is contained in:
@@ -714,13 +714,7 @@ export class LoginService {
|
||||
apiKeyResult.apiKey!
|
||||
);
|
||||
|
||||
// 4. 更新内存关联
|
||||
await this.zulipAccountService.linkGameAccount(
|
||||
user.id.toString(),
|
||||
zulipAccount.zulipUserId,
|
||||
zulipAccount.zulipEmail,
|
||||
apiKeyResult.apiKey!
|
||||
);
|
||||
// 注意:不在登录时建立内存关联,Zulip客户端将在WebSocket连接时创建
|
||||
|
||||
const duration = Date.now() - startTime;
|
||||
|
||||
|
||||
@@ -533,15 +533,7 @@ export class RegisterService {
|
||||
status: 'active',
|
||||
});
|
||||
|
||||
// 6. 建立游戏账号与Zulip账号的内存关联(用于当前会话)
|
||||
if (finalApiKey) {
|
||||
await this.zulipAccountService.linkGameAccount(
|
||||
gameUser.id.toString(),
|
||||
createResult.userId, // 已在上面验证不为 undefined
|
||||
createResult.email!,
|
||||
finalApiKey
|
||||
);
|
||||
}
|
||||
// 注意:不在注册时建立内存关联,Zulip客户端将在WebSocket连接时创建
|
||||
|
||||
const duration = Date.now() - startTime;
|
||||
|
||||
|
||||
Reference in New Issue
Block a user