commit | ed0ba901e19d711e1fe3e03344b3ba153a4859d8 | [log] [tgz] |
---|---|---|
author | Sam Rawlins <srawlins@google.com> | Fri Jun 22 18:40:05 2018 +0000 |
committer | commit-bot@chromium.org <commit-bot@chromium.org> | Fri Jun 22 18:40:05 2018 +0000 |
tree | a857a57351d62b8fa756a8962e88b71aff209f07 | |
parent | 4c697085bef9b91c371af3b766d18b0760787e10 [diff] |
Doc - Fix library links in analyzer docs These new links are stil brittle; if dartdoc changes the paths of libraries, or if `element.dart` gets a `library` directive. But at least they're fixed. There doesn't appear to be a less brittle solution. Bug: https://github.com/dart-lang/sdk/issues/27994 Change-Id: Ibff7c01442d10e7133e68500219ac9a5713888b2 Reviewed-on: https://dart-review.googlesource.com/61913 Reviewed-by: Janice Collins <jcollins@google.com> Commit-Queue: Samuel Rawlins <srawlins@google.com>
Dart is an open-source, scalable programming language, with robust libraries and runtimes, for building web, server, and mobile apps.
Visit the dartlang.org to learn more about the language, tools, getting started, and more.
Browse pub.dartlang.org for more packages and libraries contributed by the community and the Dart team.
If you want to build Dart yourself, here is a guide to getting the source, preparing your machine to build the SDK, and building.
There are more documents on our wiki.
The easiest way to contribute to Dart is to file issues.
You can also contribute patches, as described in Contributing.