Property using `declare` prompts to add 'override' even though that does not seem valid

[mjbvz]

Bug Report

🔎 Search Terms

• noImplicitOverride
• static

🕗 Version & Regression Information

4.3.0-dev.20210406

💻 Code

Using --noImplicitOverride:

export class Foo{
    kind = 1;
}

class SubFoo extends Foo{
    declare kind: undefined;
}

🙁 Actual behavior

On declare kind: undefined, I see:

This member must have an 'override' modifier because it overrides a member in the base class 'Foo'

Adding override makes the code invalid

🙂 Expected behavior

We should probably change our code to:

class SubFoo extends Foo{
    override kind: undefined;
}

However using declare was previously valid and the current error message seems incorrect

[fregante]

If anyone lands here from Google, you can either:

• add "noImplicitOverride": false to your tsconfig (just to silence it temporarily)
• add the override keyword to the methods TypeScript mentions

[Hatem-Nofal]

If anyone lands here from Google, you can either:

• add "noImplicitOverride": false to your tsconfig (just to silence it temporarily)
• add the override keyword to the methods TypeScript mentions

"* add "noImplicitOverride": false to your tsconfig (just to silence it temporarily)" => it's work thanks

[BenRacicot]

I noticed that public does not cause TS to give this error. private was.