TypeScript问题：判断可选字段存在后仍无法赋值给Required类型

TypeScript的类型收窄机制不会因为你单独检查了对象的某个可选属性存在，就自动把整个对象的类型从带可选属性的类型收窄到全属性必选的类型。哪怕你通过if(expense._id)确认了_id存在，TypeScript默认也无法保证后续代码不会把_id重新设为undefined（虽然这个场景里是局部变量不会出现，但类型系统不会做这种场景假设），所以它不会自动将expense的类型从PatchExpenseDto升级为Required<PatchExpenseDto>。

这里提供几种实用的解决思路：

1. 自定义类型守卫函数（最严谨） #

写一个类型守卫函数，明确告诉TypeScript什么样的PatchExpenseDto符合Required<PatchExpenseDto>的类型：

// 定义类型守卫
function isExistingExpense(expense: PatchExpenseDto): expense is Required<PatchExpenseDto> {
  return expense._id !== undefined;
}

// 使用守卫判断
async patchMultiple(expenses: PatchExpenseDto[]) {
  const currentExpenses: Required<PatchExpenseDto>[] = [];
  const newExpenses: PatchExpenseDto[] = [];

  expenses.forEach(expense => {
    if (isExistingExpense(expense)) {
      currentExpenses.push(expense); // 不再报错
    } else {
      newExpenses.push(expense);
    }
  });
}

这种方式是TypeScript推荐的类型收窄方式，类型安全且可读性高。

2. 类型断言（快速解决） #

如果你能确保if(expense._id)判断后_id一定存在，可以直接用类型断言跳过类型检查：

async patchMultiple(expenses: PatchExpenseDto[]) {
  const currentExpenses: Required<PatchExpenseDto>[] = [];
  const newExpenses: PatchExpenseDto[] = [];

  expenses.forEach(expense => {
    if (expense._id) {
      currentExpenses.push(expense as Required<PatchExpenseDto>); // 断言类型
    } else {
      newExpenses.push(expense);
    }
  });
}

注意：这种方式需要你自己保证逻辑的正确性，TypeScript不会再做类型校验，如果后续逻辑修改导致_id可能为undefined，会埋下运行时隐患。

3. 重组对象并明确类型 #

通过解构赋值提取_id，再重组对象，让TypeScript能明确识别_id的必选性：

async patchMultiple(expenses: PatchExpenseDto[]) {
  const currentExpenses: Required<PatchExpenseDto>[] = [];
  const newExpenses: PatchExpenseDto[] = [];

  expenses.forEach(expense => {
    const { _id, ...rest } = expense;
    if (_id) {
      // 重组后_id是必选的，符合Required类型
      currentExpenses.push({ _id, ...rest } as Required<PatchExpenseDto>);
    } else {
      newExpenses.push(expense);
    }
  });
}

这种方式相当于手动构造了符合Required<PatchExpenseDto>类型的对象，类型安全且逻辑清晰。

内容的提问来源于stack exchange，提问作者vy.pham