comment_references lint doesn't support dartdoc's idea of "in scope"

[Hixie]

As of dart-lang/dartdoc#1153, dartdoc considers pretty much everything it knows about to be in scope regardless of whether it's in scope at the Dart level. Unfortunately, the comment_references lint doesn't follow the same convention. So, for example, packages/flutter/lib/painting.dart in flutter's repo ends up flagging the three terms in the library docs ([TextPainter], [Decoration], etc) even though those are valid. This makes the lint unusable for our purposes, even though it actually catches a bunch of errors so we would love to use it.

[zoechi]

the comment_references lint doesn't follow the same convention

Don't you think it should?

Do you plan to file an issue in https://github.com/dart-lang/linter/issues?

[Hixie]

Wow I totally filed that in the wrong repo, my bad.

[Hixie]

dart-lang/linter#1142

[github-actions]

This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.