-
Notifications
You must be signed in to change notification settings - Fork 127
Closed
Labels
P0A serious issue requiring immediate resolutionA serious issue requiring immediate resolutioncustomer-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
Sometimes, a library, like the Flutter rendering library, wants to refer to another library, like the Flutter widgets library, in the documentation, but doesn't want to introduce a dependency in the code. In this case, for example, we definitely do not want any sort of runtime relationship from the rendering library to the widgets library.
We can't use import
for this because it risks code accidentally depending through the import.
One possible solution would be to have something like /// @import
which would cause the dartdoc code to import it. Another would be for the dartdoc tool to be able to receive a list of imports to imply at the top of every file. I don't really mind how we solve this.
Metadata
Metadata
Assignees
Labels
P0A serious issue requiring immediate resolutionA serious issue requiring immediate resolutioncustomer-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