Skip to content

Many unresolved-doc-reference warnings for generic types #1520

@kevmoo

Description

@kevmoo

This is a lot of noise when trying to find real bugs in doc comments.

Also, in the case of Future<Response> below, it'd be nice if Response was linked to the right type in the package.

Just for pkg/shelf:

unresolved doc reference [Future<Response>]
unresolved doc reference [List<int>]
unresolved doc reference [List<int>]
unresolved doc reference [List<int>]
unresolved doc reference [List<int>]
unresolved doc reference [List<int>]
unresolved doc reference [List<int>]
unresolved doc reference [List<int>]
unresolved doc reference [List<int>]
unresolved doc reference [List<int>]
unresolved doc reference [List<int>]
unresolved doc reference [List<int>]
unresolved doc reference [Stream<HttpRequest>]
unresolved doc reference [Stream<List<int>>]
unresolved doc reference [Stream<List<int>>]
unresolved doc reference [Stream<List<int>>]
unresolved doc reference [Stream<List<int>>]
unresolved doc reference [Stream<List<int>>]
unresolved doc reference [Stream<List<int>>]
unresolved doc reference [Stream<List<int>>]
unresolved doc reference [Stream<List<int>>]
unresolved doc reference [Stream<List<int>>]
unresolved doc reference [Stream<List<int>>]
unresolved doc reference [Stream<List<int>>]
unresolved doc reference [StreamChannel<List<int>>]

Metadata

Metadata

Assignees

No one assigned

    Labels

    P2A bug or feature request we're likely to work ontype-enhancementA request for a change that isn't a bug

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions