commit | 9c21c2c0288bc7f6db68d2f22610f56e47d63f5b | [log] [tgz] |
---|---|---|
author | Nate Bosch <nbosch1@gmail.com> | Mon Feb 25 12:07:31 2019 -0800 |
committer | GitHub <noreply@github.com> | Mon Feb 25 12:07:31 2019 -0800 |
tree | a4988e03a413ff608e36d4b8bdd40727b844ff8e | |
parent | c61d7cfeed4d61b21924e5998c73c9a3c605a3e9 [diff] |
Run dartfmt --fix (#25) Add lints for unnecessary new and const.
A package that defines a common class, PackageResolver
, for defining how to resolve package:
URIs. This class may be based on the current isolate's package resolution strategy, but it may also be explicitly defined by the user—for example, you could create a resolver that represents the strategy used to compile a .dart.js
file.
The Dart VM provides two mutually exclusive means of resolving package:
URIs: a package spec and a package root.
A package spec usually comes in the form of a .packages
file on the filesystem. It defines an individual root URL for each package name, so that package:$name/$path
resolves to $root/$path
.
A package root is a single URL that acts as the base for all package:
URIs, so that package:$name/$path
resolves to $base/$name/$path
.
This normalizes access to these resolution schemes, and makes it easy for code to resolve package URIs no matter where the resolution information comes from.