Input properties initialized with literal values containing the prohibited prefix were being incorrectly flagged, causing code like:

// the prefix is "on"
@Component()
class Test {
  @Input() notOn: string = 'on';
}

To trigger on the initializer

That happened because the selector matched any literal or identifier that were children of property definitions.

So the fix could either be in the selector or once the match already happened. I went with the latter.

I added 3 test cases, one valid with the disalowed prefix in the initializer instead of the property name and two invalids with the initializer not being matched,