Always use relative paths to import from within the front end

The style guide says to "PREFER relative paths when importing
libraries within your own package’s lib directory".  Mixing them with
package: imports doesn't work.  Before: we had a mix.  Now: we don't.

Change-Id: Iadcf1dda7bae51121e325f5d4b8c6add8759da95
Reviewed-on: https://dart-review.googlesource.com/68082
Commit-Queue: Kevin Millikin <kmillikin@google.com>
Reviewed-by: Dmitry Stefantsov <dmitryas@google.com>
Reviewed-by: Alexander Thomas <athom@google.com>
26 files changed
tree: b426c6cb6e78f77bf9f20bfdbd998347fbfc8063
  1. .clang-format
  2. .gitattributes
  3. .gitconfig
  4. .github/
  5. .gitignore
  6. .gn
  7. .mailmap
  8. .packages
  9. AUTHORS
  10. BUILD.gn
  11. CHANGELOG.md
  12. DEPS
  13. LICENSE
  14. PATENTS
  15. PRESUBMIT.py
  16. README.dart-sdk
  17. README.md
  18. WATCHLISTS
  19. build/
  20. client/
  21. codereview.settings
  22. dartdoc_options.yaml
  23. docs/
  24. pkg/
  25. runtime/
  26. samples-dev/
  27. samples/
  28. sdk/
  29. tests/
  30. third_party/
  31. tools/
  32. utils/
README.md

Dart

Dart is an open-source, scalable programming language, with robust libraries and runtimes, for building web, server, and mobile apps.

Using Dart

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.

Building Dart

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.

Contributing to Dart

The easiest way to contribute to Dart is to file issues.

You can also contribute patches, as described in Contributing.

License & patents

See LICENSE and PATENTS.