fix(user): make lastMessageAt nullable to handle new backend response
This commit is contained in:
@@ -20,7 +20,7 @@ export class User {
|
||||
declare readonly personalityTraits: PersonalityTraits;
|
||||
declare readonly preferredLanguage: string;
|
||||
declare readonly createdAt: string;
|
||||
declare readonly lastMessageAt: string;
|
||||
declare readonly lastMessageAt: string | null;
|
||||
declare readonly avatarUrl: string;
|
||||
declare readonly loginProvider: string;
|
||||
declare readonly isGuest: boolean;
|
||||
|
||||
@@ -17,7 +17,8 @@ export const UserSchema = z.object({
|
||||
personalityTraits: PersonalityTraitsSchema.default(PERSONALITY_TRAITS_DEFAULTS),
|
||||
preferredLanguage: z.string().default(""),
|
||||
createdAt: z.string().default(""),
|
||||
lastMessageAt: z.string().default(""),
|
||||
// 后端**新**游客返回 null("还没发过消息"),`.default("")` **不**兜 null —— 需 nullable
|
||||
lastMessageAt: z.string().nullable().default(null),
|
||||
avatarUrl: z.string().default(""),
|
||||
loginProvider: z.string().default("email"),
|
||||
isGuest: z.boolean().default(false),
|
||||
|
||||
Reference in New Issue
Block a user