TypeScript异构Map动态索引报错及类型限制探讨

问题概述 #

在使用TypeScript存储测试模拟数据时，采用了值类型不统一的异构Map结构，硬编码访问common、monthly等字段时类型检查正常，但通过运行时变量specific动态访问字段时，触发类型错误。

报错信息 #

● Test suite failed to run

    test/db/mongoose/mocks/loadOffersTestsPrefill.ts:178:19 - error TS7053: Element implicitly has an 'any' type because expression of type 'string' can't be used to index type '{}'.
      No index signature with a parameter of type 'string' was found on type '{}'.

    178     otherFields = mockDef?.[specific] as Record<string, unknown>;

核心代码逻辑 #

原本使用Map存储异构模拟数据，每个键对应的值是自由格式对象，供preparePredefinedOffer方法构建真实对象：

MOCKS.set(OFFER_GROUP.VipSeoBackLinks, {
  common: {
    cycle: "monthly",
    offerGroup: "VIP_BACK_LINK",
    tags: ["vip"]
  },
  _1_article: {
    name: "1 article/month",
    overridingKey: "1link",
    price: 640,
    tokenCount: 1
  },
  _2_articles: {
    name: "2 articles/month",
    overridingKey: "2links",
    price: 1280,
    tokenCount: 2
  }
});

async function preparePredefinedOffer(
  offerDao: IOfferDao<ObjectId, IOffer<ObjectId>>,
  offerGroup: OFFER_GROUP,
  specific?: string,
) {
  const mockDef = MOCKS.get(offerGroup);
  const { common, monthly, yearly } = mockDef as Record<
    string,
    Record<string, unknown>
  >;
  let otherFields: Record<string, unknown>;

  if (specific == null) {
    otherFields = {};
  } else if (specific == "m") {
    otherFields = monthly;
    otherFields.offerGroup = offerGroup;
    otherFields.cycle = "monthly";
    otherFields.overridingKey = "monthly-" + offerGroup;
  } else if (specific == "y") {
    otherFields = yearly;
    otherFields.offerGroup = offerGroup;
    otherFields.cycle = "yearly";
    otherFields.overridingKey = "yearly-" + offerGroup;
  } else {
    otherFields = mockDef?.[specific] as Record<string, unknown>;
    if (otherFields == null) {
      console.warn(
        "No special field found in mock ",
        offerGroup,
        " with key: ",
        specific,
      );
    }
  }
  const offer = offerDao.build({
    ...baseRootOffer,
    ...common,
    ...otherFields,
  });

  return offer;
}

已验证的解决方案 #

将Map替换为普通对象，并通过自定义类型描述异构结构，解决动态索引的类型问题：

自定义类型定义 #

type MockType = {
  [key in OFFER_GROUP]: {
    [subKey: string]: any;
  };
};

// 提取MockType中所有值类型的联合类型
type UnionFromMockType<T> = T extends {
    [K in keyof T]: infer U;
  }
  ? U
  : never;

type CompleteMockType = UnionFromMockType<MockType[OFFER_GROUP]>;

修改后的MOCKS与函数实现 #

const MOCKS: MockType = {
  Free: {},
  Startup: {
    common: {},
    monthly: {
      price: 49,
      tags: ["subscription", "standard", "monthly"]
    },
    yearly: {
      price: 490,
      tags: ["subscription", "standard", "yearly"]
    }
  },
  // 其他OFFER_GROUP对应的模拟数据...
};

async function preparePredefinedOffer(
  offerDao: IOfferDao<ObjectId, IOffer<ObjectId>>,
  offerGroup: OFFER_GROUP,
  specific?: string,
) {
  const mockDef: CompleteMockType = MOCKS[offerGroup];
  const { common, monthly, yearly } = mockDef;
  let otherFields: Record<string, unknown>;

  // 后续逻辑保持不变...
}

关于TypeScript对Map的限制疑问解答 #

TypeScript并没有“大幅限制”JavaScript的Map，只是其类型系统要求明确性：

• 原生Map的默认类型是同构的（即所有键值对的键类型、值类型统一），比如Map<K, V>中所有值都是V类型。
• 如果要让Map支持异构值，可以通过自定义泛型实现，比如Map<OFFER_GROUP, Record<string, unknown>>，但这种方式在动态索引时仍需额外的类型断言。
• 相比之下，普通对象更适合这种异构场景，因为可以通过索引签名、映射类型更灵活地描述不同键对应的值结构，无需额外断言即可通过类型检查。

内容的提问来源于stack exchange，提问作者Zied Hamdi