Extending a class method with prototype assignment confuses the compiler about membership type

[mohsen1]

This is an issue I encountered when working on webpack/webpack#6862

Bug Repository

See the bug repo for complete code
https://github.com/mohsen1/ts-bug-instance-member

Run npm test to run the test

Expected behavior:
No Error
Actual behavior:

index.js:7:19 - error TS2424: Class 'Ex' defines instance member function 'foo', but extended class 'MyClass' defines it as instance member property.

7 MyClass.prototype.foo = function() {
                    ~~~

[sandersn]

Fix is up at #22935

[mohsen1]

@sandersn using the nightly I'm still getting the error

mohsen1/ts-bug-instance-member#1

[sandersn]

I see, it looks like it breaks going the other direction, when the base uses prototype assignment. I’ll take anothe look.

[sandersn]

Well, actually it turns out that it's the arrow function being used as a method. This is ... weird, but technically correct as long as the author remembers that this isn't an instance of Ex. I'll have a fix up shortly; I see a couple of ways to do it.

[sandersn]

Note that --noImplicitThis works with "checkJs": true, but it marks every usage of this outside a class, which makes it hard to use transitionally. So recognising arrow functions as methods is good for understanding existing code, but bad in that it doesn't prevent js authors from possibly buggy new code.

I think the right thing is to prefer understanding existing code, since we hope people with write new code in Typescript. They will, at least, have years of experience lowering their expectations of the correctness of any new Javascript that they write.

[sandersn]

OK, the fix is merged. @mohsen1 can you try typescript@next tomorrow?