Skip to content

unintended_html_in_doc_comment false positives? #59516

@goderbauer

Description

@goderbauer

In the following doc comment the unintended_html_in_doc_comment lint fires on [Tween<Offset>] and Tween<T> even though the docs render correctly.

/// You can also use [Tween<int>].
/// And have you seen `Tween<T>`?
class Tween<T> {
}

(For the correct rendering of these references search for them on https://main-api.flutter.dev/flutter/animation/Tween-class.html).

At least the reference in ` should not trigger the lint (which would be in line with what is documented: https://dart.dev/tools/linter-rules/unintended_html_in_doc_comment).

I was a little surprised that the reference in [] triggers the lint (as documented) since it seems to render totally fine.

Metadata

Metadata

Assignees

No one assigned

    Labels

    P2A bug or feature request we're likely to work onarea-devexpFor issues related to the analysis server, IDE support, linter, `dart fix`, and diagnostic messages.devexp-linterIssues with the analyzer's support for the linter packagelinter-false-positiveIssues related to lint rules that report a problem when it isn't a problem.type-bugIncorrect behavior (everything from a crash to more subtle misbehavior)

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions