Typescript name collision/clash using multiple interface inheritance

Question

If in Typescript I have two interfaces which both have a member of same name, how can I securly implement both interfaces? Is this even possible?

Example:

interface IFace1 {
    name: string;
}
interface IFace2 {
    name: string;
}

class SomeClass extends IFace1, IFace2 {
    // How to implement IFace1.name and IFace2.name ??
}

I know in C# this can be resolved and works because of C#'s type information at runtime, but what about Typescript?

TypeScript has no way to support this because the interface is a pure compile-time mechanism. The resulting JavaScript has no concept of the interface, the interface is erased. Given that, what would be your expected behavior to make this work? — vcsjones
– vcsjones, Commented Dec 16, 2013 at 20:09

Ryan Cavanaugh · Accepted Answer · 2013-12-16 20:11:30Z

4

TypeScript uses a structural type system, so there's absolutely no difference between IFace1 and IFace2. You would implement them like this:

class SomeClass implements IFace1, IFace2 {
    name = 'foo';
}

As vcsjones mentioned, because there is no runtime type information, there's not a plausible way where this could work on a nominal basis.

answered Dec 16, 2013 at 20:11

Ryan Cavanaugh

223k59 gold badges280 silver badges235 bronze badges

Sign up to request clarification or add additional context in comments.

2 Comments

Dynalon Over a year ago

Yes, I thought that this would be the case. But how to deal with it then? It is a real-world problem. I'll create another question (as this one is perfectly answered) describing the problems and asking for how to work around them ;)

LuckyLikey Over a year ago

the concept behind it is also very nicely explained here

Collectives™ on Stack Overflow

Typescript name collision/clash using multiple interface inheritance

1 Answer 1

2 Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

2 Comments

Your Answer

Sign up or log in

Post as a guest

Related