-
Notifications
You must be signed in to change notification settings - Fork 1.7k
DartDoc: Add a link from class page to full source code. #8860
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Removed Type-Defect label. |
This comment was originally written by [email protected] To be fixed in next gen doc viewer. Marked this as being blocked by #8857. |
Added old-dartdoc label. |
Issue #5793 has been merged into this issue. |
In general it would be good to have a mechanism for showing code inline as well as the possibility to link to the full sources. |
This comment was originally written by [email protected] The old Dart doc had this. But I didn't find it very useful due to the convention in the Dart source of splitting the public interface and private implementation. So you usually only got to see the method signature not the actual implementation. Ideally there would be some way of easily getting to the actual implementation. |
Added Pkg-DartDoc label. |
Removed Area-DartDoc label. |
Removed Pkg-DartDoc label. |
I think this can be closed. The current docs at dartdocs.org and at api.dartlang.org have breadcrumbs back to the library where a class was defined. See: http://www.dartdocs.org/documentation/args/0.12.0+2/index.html#args/args.ArgParser |
Moved over to dart-lang/dartdoc#73 Added MovedToGithub label. |
This issue was originally filed by [email protected]
It would be nice to have a link from a class page on api.dartlang.org to the full source file where the class is defined.
Either a link to browse source on code.google.com, or embedding the source within api.dartlang.org.
Bonus points - if it is a abstract class, if you can add a link to the private class (or classes) that implement the interface.
Docs are nice, but easily accessible open source code is even better ;)
The text was updated successfully, but these errors were encountered: