Janice Collins
Janice Collins
> However, it's still useful to have a library declaration for a number of reasons: > > * Adding annotations/metadata to the library. > * Writing documentation for the library....
@bwilkerson @srawlins Is there something in the analyzer blocking this?
Probably listing all source files would be too much. I think what would be nice for my particular case is knowing what modules get built (even if there are many...
I don't actually know much about how ddc works with the build system, which is why this information would be helpful -- let me know if my terminology is incorrect...
This is as designed. We could add an option to document these, however.
There is no update as yet, but since there's been continuing traffic on this feature request, elevating to P2.
It sounds like the general trend is to desire documentation for all private library members in a library or even package. If it is going to be at the library...
Since annotations can be present on libraries, if we do both probably the dartdoc_options version would be limited to entire packages or directory trees. This would also be a good...
> > A bug where src libraries exported under lib are treated as separate libraries. > > Hmm, what does dartdoc do today for public libraries in this situation? For...
Impact of this was reduced significantly as a side effect of #1865. Now it only runs a few times (technically, it runs as many times as the number of subdirectories...