You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
These split declarations are seen as two declarations by VS Code, which doesn't work very well, e.g. doesn't show you the interface members in the pop-up:
Can't you merge these?
The text was updated successfully, but these errors were encountered:
Why are the declarations in lib.d.ts split into two?
The reason is rather historic. back in 0.8.* time classes and interfaces did not merge, and we wanted these classes to be extensible.
The other part that makes blocks this conversion across the board is call signatures. there is no way now to define a call signature on a class. this is tracked by #183.
As @plantain-00 noted; the result of the split should not be of any much consequence. moving to classes, would allow extending the static side, which is not allowed now. not sure that this is a common scenario however.
Can't you merge these?
They can. I do agree it makes the declaration file cleaner and easier to read. this request is tracked by #574
Why are the declarations in
lib.d.ts
split into two?Why isn't this declared as a class?
These split declarations are seen as two declarations by VS Code, which doesn't work very well, e.g. doesn't show you the interface members in the pop-up:
Can't you merge these?
The text was updated successfully, but these errors were encountered: