Open
Description
🔎 Search Terms
literal intersection branded string
🕗 Version & Regression Information
- This is the behavior in every version I tried, and I reviewed the FAQ for entries about branded strings/literal intersections.
⏯ Playground Link
💻 Code
declare const typeKey: unique symbol;
type TypeID<Type = unknown, ID extends string = string> = ID & { [typeKey]?: Type };
function typeID<Type, ID extends string>(id: ID): TypeID<Type, ID> {
return id;
}
type KeyOf<TID extends TypeID> = TID extends TypeID<any, infer ID> ? ID : never;
type TypeOf<TID extends TypeID> = TID extends TypeID<infer Type> ? Type : never;
type Provides<P extends TypeID> = { readonly [T in KeyOf<P>]: TypeOf<P> };
// ---cut---
interface Foo {
foo(): void;
}
const Foo = typeID("Foo") satisfies TypeID<Foo>;
// ^? const Foo: TypeID<Foo, "Foo">
const Bar: Provides<typeof Foo> = {
[Foo]: {
foo() {}
}
};
🙁 Actual behavior
Fails to compile with error:
Property 'Foo' is missing in type '{ [x: string]: { foo(): void; }; }' but required in type 'Provides<TypeID<Foo, "Foo">>'.
🙂 Expected behavior
I'd expect it to compile. Rather than widening the literal type to string
, I'd expect it to discard the { [typeKey]?: Type }
part, since that's pretty much bogus at runtime anyway.
However, it should also not lose the type information for the generic types. For instance, if I change the declaration to...
type TypeID<Type = unknown, ID extends string = string> = ID;
...then it does compile, but so does this...
const Bar: Provides<typeof Foo> = {
[Foo]: {
// No error about missing member `foo` here!
}
};
Additional information about the issue
Possibly related to #43852 (comment)