| tag | 697af5f386547ef60fb1d796b606b41e35da4a8d | |
|---|---|---|
| tagger | Natalie Weizenbaum <nweiz@google.com> | Fri May 25 11:55:54 2018 -0400 |
| object | ce0f41eba9ba9e50500a7ffec373061cfc0edc76 |
Use Dart 2 constants.
| commit | ce0f41eba9ba9e50500a7ffec373061cfc0edc76 | [log] [tgz] |
|---|---|---|
| author | Lasse R.H. Nielsen <lrn@google.com> | Tue May 22 14:56:28 2018 +0200 |
| committer | GitHub <noreply@github.com> | Tue May 22 14:56:28 2018 +0200 |
| tree | bf625f3262a4f40ee9187cc7c646b3f55941fd98 | |
| parent | 2c1d30a175bdc2a71200bb503e012319776c9b47 [diff] |
Remove upper case constants (#13) * Remove upper case constants Add dev-dependency directly on stack_trace package. Imported the package, but relied on an indirect dependency to ensure that the package was available.
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.