Forbid abstract property to have an initializer in parser instead of semantic

[fisker]

class Foo {
  abstract prop = 3;
}

[ulrichstark]

Also the same for methods and property accessors probably, or?

abstract class Foo {
  abstract method() {}

  abstract get accessor() {
    return 1;
  }
}

[fisker]

Also the same for methods and property accessors probably, or?

I'd align with typescript-eslint, if they do, we follow, if not, ask them to do it first. (On cellphone, didn't test myself)

[ulrichstark]

I'd align with typescript-eslint, if they do, we follow, if not, ask them to do it first. (On cellphone, didn't test myself)

I'm not sure how to spot the difference in the handling of typescript-eslint. It seems like only the initialization of an abstract property is an hard error on their side (TSEslint Playground). This behavior was introduced by you in typescript-eslint/typescript-eslint#6613.

Could you please decide what's the case and report appropriately to them? I will then implement the required change here in OXC.

Also while researching for this issue, I found a duplicate reported diagnostic for the implementation of abstract methods: #14193

[fisker]

typescript-eslint/typescript-eslint#11653 and typescript-eslint/typescript-eslint#11654