Closed
Description
This is likely tied up in Sky's pattern of using unnamed libraries (which we may need to change if we're just fighting the tools). See dart-lang/sdk#22836 for other discussion on the issue.
But the following library:
test/lib/one.dart
:
class One {}
Will produce a warning:
generating docs for library one from one.dart...
warning: library 'one' has no documentation
Which will require a library one;
statement to solve:
/// Library docs!
library one;
class One{}
I would recommend clarifying the warning to explain that the library is unnamed and ideally make it possible to document a library w/o adding a library name;
statement.