Subclass property incorrectly reported as write-only

[nex3]

In the following code:

class Super {
  get foo {}
  set foo(_) {}
}

class Sub extends Super {
  set foo(_) {}
}

The documentation for Sub claims that foo is write-only, despite it extending Super and thus supporting Super.foo as a readable property.

This has comes up in practice with the LineScanner class, whose position field is documented as write-only despite extending SpanScanner. It's also worth noting that LineScanner.position fails to inherit the documentation for SpanScanner.position, although this is probably just the same issue.

[jcollins-g]

Dartdoc has known bugs with half-field inheritance and this behavior is the result.

[jcollins-g]

This is now fixed with #1466.