-
Notifications
You must be signed in to change notification settings - Fork 127
Closed
Labels
P1A high priority bug; for example, a single project is unusable or has many test failuresA high priority bug; for example, a single project is unusable or has many test failurescustomer-flutterIssues originating from important to FlutterIssues originating from important to Fluttertype-enhancementA request for a change that isn't a bugA request for a change that isn't a bug
Description
When a library exports another library, but both libraries are being docced together, the result is that each class that is exported by both libraries is listed twice.
We should only list classes as coming from the package that they actually come from, and not mention them in packages that re-export them, if we are including that package in the docs.
See also:
- don't link to exported name if original location is public and inside same package #1090 (about where the links to reexported symbols should point)
- Exported classes don't have any indication where they come from #936 (about saying where types come from when reexported)
- For Flutter docs, be more aggressive about including dependencies #1159 (about automatically documenting even non-exported libraries)
cc @devoncarew
Metadata
Metadata
Assignees
Labels
P1A high priority bug; for example, a single project is unusable or has many test failuresA high priority bug; for example, a single project is unusable or has many test failurescustomer-flutterIssues originating from important to FlutterIssues originating from important to Fluttertype-enhancementA request for a change that isn't a bugA request for a change that isn't a bug