| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
添加ohos平台 Signed-off-by: cjand <1747143535@qq.com> | 2 年前 | |
[platform] Import the platform package (#4613) Imports the packages platform from https://github.com/google/platform.dart - As there is not much history in the package, this imports it as a copy instead of going through the process of actually merging the commit history of that repo into this one. - The only changes relative to the current source in that repo are: - Adjustments for repo conventions (such as removing analysis_options.yaml and fixing the resulting issues). - Addressing https://github.com/google/platform.dart/pull/44 Part of https://github.com/flutter/flutter/issues/130915 | 3 年前 | |
[platform] Import the platform package (#4613) Imports the packages platform from https://github.com/google/platform.dart - As there is not much history in the package, this imports it as a copy instead of going through the process of actually merging the commit history of that repo into this one. - The only changes relative to the current source in that repo are: - Adjustments for repo conventions (such as removing analysis_options.yaml and fixing the resulting issues). - Addressing https://github.com/google/platform.dart/pull/44 Part of https://github.com/flutter/flutter/issues/130915 | 3 年前 | |
[platform] Import the platform package (#4613) Imports the packages platform from https://github.com/google/platform.dart - As there is not much history in the package, this imports it as a copy instead of going through the process of actually merging the commit history of that repo into this one. - The only changes relative to the current source in that repo are: - Adjustments for repo conventions (such as removing analysis_options.yaml and fixing the resulting issues). - Addressing https://github.com/google/platform.dart/pull/44 Part of https://github.com/flutter/flutter/issues/130915 | 3 年前 | |
[all] Add topics to pubspecs (#4771) Adds [topics](https://dart.dev/tools/pub/pubspec#topics) to all packages, supporting the new pub feature for categorizing packages. The heuristics I used were: - Try to use existing topics from https://pub.dev/topics where applicable - Add new topics as necessary to cover things that seemed like obvious relevant topics - Include the plugin name as a topic for all federated plugin packages, for grouping (since pub doesn't inherently group or cross-link implementations) This is not an attempt to be exhaustive; as topics evolve I expect we will add more or adjust. Also updates the repo tooling to enforce topics, so that we don't forget to add them to new packages. The enforced rule is: - All packages must have at least one topic. We could potentially change this to allow an empty topics section so that we are enforcing that we didn't just forget to add the section, but in practice even for packages that we don't expect people to be likely to use, I didn't have any issue coming up with at least one relevant topic. - Federated plugin packages must contain the plugin name as a topic. While this isn't time-critical, I chose to include version bumps so that we aren't rolling out topics in a piecemeal way (e.g., with only a random subset of a federated plugin's packages having topics on pub.dev based on what has happened to have a bugfix). | 3 年前 | |
[platform] Import the platform package (#4613) Imports the packages platform from https://github.com/google/platform.dart - As there is not much history in the package, this imports it as a copy instead of going through the process of actually merging the commit history of that repo into this one. - The only changes relative to the current source in that repo are: - Adjustments for repo conventions (such as removing analysis_options.yaml and fixing the resulting issues). - Addressing https://github.com/google/platform.dart/pull/44 Part of https://github.com/flutter/flutter/issues/130915 | 3 年前 | |
[platform] Import the platform package (#4613) Imports the packages platform from https://github.com/google/platform.dart - As there is not much history in the package, this imports it as a copy instead of going through the process of actually merging the commit history of that repo into this one. - The only changes relative to the current source in that repo are: - Adjustments for repo conventions (such as removing analysis_options.yaml and fixing the resulting issues). - Addressing https://github.com/google/platform.dart/pull/44 Part of https://github.com/flutter/flutter/issues/130915 | 3 年前 | |
[platform] Import the platform package (#4613) Imports the packages platform from https://github.com/google/platform.dart - As there is not much history in the package, this imports it as a copy instead of going through the process of actually merging the commit history of that repo into this one. - The only changes relative to the current source in that repo are: - Adjustments for repo conventions (such as removing analysis_options.yaml and fixing the resulting issues). - Addressing https://github.com/google/platform.dart/pull/44 Part of https://github.com/flutter/flutter/issues/130915 | 3 年前 | |
[all] Add topics to pubspecs (#4771) Adds [topics](https://dart.dev/tools/pub/pubspec#topics) to all packages, supporting the new pub feature for categorizing packages. The heuristics I used were: - Try to use existing topics from https://pub.dev/topics where applicable - Add new topics as necessary to cover things that seemed like obvious relevant topics - Include the plugin name as a topic for all federated plugin packages, for grouping (since pub doesn't inherently group or cross-link implementations) This is not an attempt to be exhaustive; as topics evolve I expect we will add more or adjust. Also updates the repo tooling to enforce topics, so that we don't forget to add them to new packages. The enforced rule is: - All packages must have at least one topic. We could potentially change this to allow an empty topics section so that we are enforcing that we didn't just forget to add the section, but in practice even for packages that we don't expect people to be likely to use, I didn't have any issue coming up with at least one relevant topic. - Federated plugin packages must contain the plugin name as a topic. While this isn't time-critical, I chose to include version bumps so that we aren't rolling out topics in a piecemeal way (e.g., with only a random subset of a federated plugin's packages having topics on pub.dev based on what has happened to have a bugfix). | 3 年前 |
A generic platform abstraction for Dart.
Like dart:io, package:platform supplies a rich, Dart-idiomatic API for
accessing platform-specific information.
package:platform provides a lightweight wrapper around the static Platform
properties that exist in dart:io. However, it uses instance properties rather
than static properties, making it possible to mock out in tests.