Kathy Walrath
Kathy Walrath
Another option is to use a non-dartdoc tool to allow people to check their doc code (with or without `///`s). Maybe a dartdoc-ish version of https://dart-lang.github.io/markdown/.
Once the page is a little more finished, we should refer to it from https://dart.dev/tools/dartdoc (and/or the pages it links to).
Yes, please. There should be an option for a search results page. For example: 1. Go to https://www.dartdocs.org/documentation/flutter/0.0.32-dev/cupertino/cupertino-library.html. You can see there's an Animatable class there. 2. Enter Animatable in...
@johnpryan @RedBrogdon maybe we should move/dupe this to the dartpad repo?
I don't know if it was ever fixed. I don't see any library comments for the stagehand docs unless I add a library statement (`library stagehand;`) above the imports. We...
Very strange. Thanks for looking into this. Please let me know if there's anything I can do to help.
I think it might be confusing to implicitly compile it as Flutter, especially if they explicitly selected to create a Dart app. The easiest solution would be to just spit...
On a separate thread, @chalin noted that webdev limits the docs for the generated libraries using the dartdoc --include/--exclude flags. He thought pub docs could do the same. @kevmoo thought...
There's a difference between documenting all the libraries and encouraging people to import only the libraries that they absolutely need. The API doc for each component could encourage using the...