In defense of interface: Using declaration merging to disable bad parts

Question

In defense of interface: Using declaration merging to disable bad parts

danvk opened this issue 2 years ago · comments

Dan Vanderkam commented 2 years ago

In defense of interface: Using declaration merging to disable bad parts

https://effectivetypescript.com/2021/06/03/interface/

Dan Vanderkam · Answer 1 · Tue Mar 01 2022 23:01:41 GMT+0800 (China Standard Time)

Comment by Serhii on 2021-07-07 09:13:

Here I have overloaded BuiltIn CallableFunction

Andy Edwards · Answer 2 · Tue May 16 2023 11:28:25 GMT+0800 (China Standard Time)

Declaration merging deserves all the hate it gets. I can’t declare a class named Plugin in one of my files because it conflicts with the DOM Plugin class? That’s user-antagonistic behavior. Local names in JS shadow global names, so it’s really annoying that TS behaves completely differently.

Andy Edwards · Answer 3 · Tue May 16 2023 11:30:05 GMT+0800 (China Standard Time)

It’s just leftover cruft from TypeScript's pre-ESM days that needs to be eradicated.

Andy Edwards · Answer 4 · Tue May 16 2023 11:32:36 GMT+0800 (China Standard Time)

Monkeypatching type definitions can be useful but there should be a way to explicitly declare overrides, instead of having to exploit an ill-conceived feature to do so.