| tag | a9d04f9bc0286de3c9c22d01f216f9c35cb7b0cc | |
|---|---|---|
| tagger | William Hesse <whesse@google.com> | Tue Jan 03 13:52:38 2017 |
| object | 2dc21b927f1dcb30b0bde45ad90980437362c7a2 |
1.0.2+1
| commit | 2dc21b927f1dcb30b0bde45ad90980437362c7a2 | [log] [tgz] |
|---|---|---|
| author | Natalie Weizenbaum <nex342@gmail.com> | Mon Oct 10 20:47:29 2016 |
| committer | GitHub <noreply@github.com> | Mon Oct 10 20:47:29 2016 |
| tree | aa648da83882bd7221f36b782d375139d5c4dd5a | |
| parent | 7cbba6d96b1d74e676164d3a7a871fbafd837c0c [diff] |
Fix a test that was broken on Mac OS X. (#2) Closes #1
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.