| commit | 489be8ce78f9dd69a0fc5a128387d74d39d6191d | [log] [tgz] |
|---|---|---|
| author | Jonas Finnemann Jensen <jonasfj@google.com> | Mon Feb 07 13:14:18 2022 +0100 |
| committer | GitHub <noreply@github.com> | Mon Feb 07 13:14:18 2022 +0100 |
| tree | ee6fa062dc4f3f8e9a58afec0d3e2c8e41f212e9 | |
| parent | b00181579ceb21cfd4d4ad013d0bb8afc2c27537 [diff] |
Fix broken link for language-versioning spec (#120) Thanks! And yes, it's an issue that files do not have permalinks, but we also do want to use the hierarchical structure of the repo for placing them where they belong, and we don't want to keep copies around, because that risks older copies being stale. No good solution found. (If only you could tag files and refer to them by tag.)
Support for working with Package Configuration files as described in the Package Configuration v2 design document.
A Dart package configuration file is used to resolve Dart package names (e.g. foobar) to Dart files containing the source code for that package (e.g. file:///Users/myuser/.pub-cache/hosted/pub.dartlang.org/foobar-1.1.0). The standard package configuration file is .dart_tool/package_config.json, and is written by the Dart tool when the command dart pub get is run.
The primary libraries of this package are
package_config.dart: Defines the PackageConfig class and other types needed to use package configurations, and provides functions to find, read and write package configuration files.
package_config_types.dart: Just the PackageConfig class and other types needed to use package configurations. This library does not depend on dart:io.
The package includes deprecated backwards compatible functionality to work with the .packages file. This functionality will not be maintained, and will be removed in a future version of this package.