开发者可通过本项目在 Flutter 应用中无缝集成常用插件，最小化业务改动获得完整 OpenHarmony 原生能力支持。项目基于 Flutter 社区官方插件库扩展，新增对 OpenHarmony 平台的兼容适配，提供多个已适配插件及使用示例。【此简介由AI生成】

openharmony_ci!1009 merge br_shared_preferences-v2.5.4_ohos into br_shared_preferences-v2.5.4_ohos

72b55a85创建于 9 天前10,297次提交

文件	最后提交记录	最后更新时间
.ci	chore: Add unit test checks. Signed-off-by: 谢代荣 <xiedairong@huawei.com>	11 天前
.gemini	Try to convince GCA to stop complaining about `dependency_overrides` (#9879) Adds a section to the review agent configuration to try to get it to stop leaving comments like [this one](https://github.com/flutter/packages/pull/9878#discussion_r2296811190) on federated plugin PRs that are following our standard, documented process.	8 个月前
.github	[ci] Use manual trigger for go_router_batch workflow for testing purp… (#10475) …oses and adjust release branch name as title ## Pre-Review Checklist Note: The Flutter team is currently trialing the use of [Gemini Code Assist for GitHub](https://developers.google.com/gemini-code-assist/docs/review-github-code). Comments from the `gemini-code-assist` bot should not be taken as authoritative feedback from the Flutter team. If you find its comments useful you can update your code accordingly, but if you are unsure or disagree with the feedback, please feel free to wait for a Flutter team member's review for guidance on which automated comments should be addressed. [^1]: Regular contributors who have demonstrated familiarity with the repository guidelines only need to comment if the PR is not auto-exempted by repo tooling.	5 个月前
packages	!924 merge br_shared_preferences-v2.5.4_ohos into br_shared_preferences-v2.5.4_ohos Fix: pinned dependency to br_shared_preferences-v2.5.4_ohos branch Created-by: weixin_46147069 Commit-by: weixin_46147069 Merged-by: openharmony_ci Description: <!-- Please remove all comments before submitting to avoid them being included in merge commit message --> ## Why are these changes being made? The HarmonyOS branch of the shared_preference dependency is not pinned, risking pulling the wrong version. ## Changelog fix: update to correct version number ## Test Plan Pull the version-pinned dependency from the respective branch for testing. ## Checklist - [x] No illegal compatibility changes are involved; if any are, they have passed the corresponding review. - [x] No performance issues are present or have been tested and there is no performance degradation. - [x] Compliant with the corresponding coding standards. - [x] No document updates are required, or the documents have been updated. - [x] In terms of testability requirements, necessary self-test cases, reasonable log recording or Trace information have been added. - [x] No illegal file introductions exist, including images and code, etc. - [x] The branches for the corresponding framework version that need to be merged have been confirmed. - [x] 3.35 - [x] 3.32 - [x] 3.27 - [x] 3.22 - [x] 3.7 See merge request: openharmony-tpc/flutter_packages!924	21 天前
script	[url_launcher] Update for UIScene compatibility (#10549) Replaces the code that attempted to find the topmost presented view controller as the context for presenting a Safari view controller with a call to the new registrar API to get the Flutter view's controller. Since it's now possible for there not to be a view controller, adds an exception for that case. This should only be possible in an add-to-app scenario where someone tries to show an in-app URL from a Flutter view that is not being displayed, which is an unlikely enough scenario that I'm not going to consider this a breaking change. Fixes https://github.com/flutter/flutter/issues/174415 ## Pre-Review Checklist [^1]: Regular contributors who have demonstrated familiarity with the repository guidelines only need to comment if the PR is not auto-exempted by repo tooling.	5 个月前
third_party	[all] Omit obvious local types (#10511) Makes the analysis options changes described in https://github.com/flutter/flutter/issues/178827: - Adding [omit_obvious_local_variable_types](https://dart.dev/tools/linter-rules/omit_obvious_local_variable_types) - Adding [specify_nonobvious_local_variable_types](https://dart.dev/tools/linter-rules/specify_nonobvious_local_variable_types) - Adding [specify_nonobvious_property_types](https://dart.dev/tools/linter-rules/specify_nonobvious_property_types) - Adding [type_annotate_public_apis](https://dart.dev/tools/linter-rules/type_annotate_public_apis) - Removing [always_specify_types](https://dart.dev/tools/linter-rules/always_specify_types) After those changes, makes the following repo-wide changes: - `dart fix --apply` in all packages and in script/tool/ - `dart format` in all packages and in script/tool/ - `update-excerpts` repo tooling command to update excerpts based on the changes to their sources Also updates the min Flutter/Dart SDK version to 3.35/3.9 for the following packages, to avoid `analyze` failures in the `N-2` legacy analysis run due to what appears to be a 3.9 change in what the Dart analyzer continues to be an obvious local type in loop iterations: - go_router - google_fonts - google_identity_services_web - google_maps_flutter_web - local_auth_platform_interface - metrics_center - multicast_dns - pigeon - rfw - shared_preferences - two_dimensional_scrollables - vector_graphics_compiler - mustache_template - path_parsing Because this is causing a significant amount of format churn already, I took this opportunity to update the repository tooling to a min Dart SDK of 3.8 (the N-2 stable version, so the earliest version we need the tooling to support) to pick up the new format style, so the amount of automated formatter change is higher in script/tool/ than in the packages. This does contain two manual changes (other than the repo tooling min version): - https://github.com/flutter/packages/commit/d700b45c7df3a79f66dc119ad36dd2bc1e042acf changes `dynamic` to `Object?` in a few places where `dynamic` caused analyzer warnings under the new rule set. - Updates the repo tooling to ignore `.dart_tool/` when looking for unexpected local `analysis_options.yaml` files, to fix issues running the repo tool's `analyze` command locally based on recent changes in `dart` behavior. This does not include any CHANGELOG or version updates; even though we normally version any changes to production code, mass automated changes like this aren't worth the churn of releasing. This includes changes to lib/example/main.dart and to README.md excerpts; while the style changes will be user-visible on pub.dev, it's fine for those changes to wait for the next release of each package. Part of https://github.com/flutter/flutter/issues/178827	6 个月前
.ci.yaml	Update repo for 3.38 (#10405) Does all of the steps from https://github.com/flutter/flutter/blob/master/docs/ecosystem/release/Updating-Packages-repo-for-a-stable-release.md for the 3.38 release (except the first one, which the stable roller will handle). This includes a lot of autoformat changes, because the N-2 is now 3.32, which means many packages are now being updated to a min Dart SDK of 3.8, triggering a formatter behavior change.	6 个月前
.ci_ohos.yaml	chore: Add unit test checks. Signed-off-by: 谢代荣 <xiedairong@huawei.com>	11 天前
.clang-format	[ci] Run analysis with older versions of Flutter (#1152)	4 年前
.gitattributes	boilerplate	8 年前
.gitignore	Ignore .cxx/ directories (#9268) Android builds now create .cxx directories in some cases; this has been added to the app template's ignore file, so should be ignored here as well. As is generally the case for this repo, we ignore it at the root level instead of updating every package.	1 年前
.metadata	[google_sign_in] Bridge google_sign_in and googleapis. (#2824) Introduce the first version of the `extension_google_sign_in_as_googleapis_auth` package. This package lets users of the `google_sign_in` plugin to create an authenticated HTTP clients (from `googleapis_auth`) that can access any APIs from the `googleapis` package.	5 年前
AGENTS.md	Instruct agents to create a repo root alias (#10165) In my trials so far, Jules struggles to run the repo tooling commands once it has moved into a target directory, because it frequently tries to use a root-relative path instead of an absolute path. To try to reduce that problem, this instructs the agent to explicitly create an alias so that the later commands that reference REPO_ROOT as a placeholder will, hopefully, be run exactly as written in the examples instead. Also, to reduce unnecessary working directory confusion, switch to `dart pub get -C` instead of `cd` followed by `dart pub get` for initializing the tooling. (Also makes the same change to the tool README, because why not have humans run one command instead of three.)	7 个月前
AUTHORS	[go_router_builder] Proposal: add json support, custom string encoder/decoder (#8665) Add initial json support for use in go_router_builder Adds annotation that enable custom string encoder/decoder, its enable conversion for base64 This allow custom type conversion for parameters, like mentionated in [#117261](https://github.com/flutter/flutter/issues/117261) and [#110781](https://github.com/flutter/flutter/issues/110781)	8 个月前
CODEOWNERS	Redistribute iOS CODEOWNERS (#10520) Redistribute iOS CODEOWNERS to rebalance load between team. ## Pre-Review Checklist Note: The Flutter team is currently trialing the use of [Gemini Code Assist for GitHub](https://developers.google.com/gemini-code-assist/docs/review-github-code). Comments from the `gemini-code-assist` bot should not be taken as authoritative feedback from the Flutter team. If you find its comments useful you can update your code accordingly, but if you are unsure or disagree with the feedback, please feel free to wait for a Flutter team member's review for guidance on which automated comments should be addressed. [^1]: Regular contributors who have demonstrated familiarity with the repository guidelines only need to comment if the PR is not auto-exempted by repo tooling.	5 个月前
CONTRIBUTING.md	Update Flutter wiki links (#6789) Updates all links to the Flutter wiki to point to their new location in the flutter/flutter repository. (The sole exception is a link to a doc that doesn't have a final home yet, and is linked from legacy code anyway so doesn't really need to be updated.) While touching the PR template, makes a few minor improvements: - Removes the breaking change discussion that doesn't apply to this repository, as breaking changes are handled totally differently for packages (and is covered by the link to docs about Dart versioning). - Adds text and a link to reflect the fact that some PRs can be changelog-exempt.	1 年前
LICENSE	Remove "All right reserved" from all files (#10066) Per guidance from legal on current preferred practice, remove "All rights reserved" from all LICENSE files and header blocks, and update the repo tool check accordingly.	7 个月前
OAT.xml	添加OAT，更新README，修改头文件 Signed-off-by: 18673122732 <liwei912744@talkweb.com.cn>	7 个月前
README.md	[mustache_template] Initial import (#9944) The `mustache_template` package has been transferred to the `flutter.dev` publisher, so this imports it into our repository and updates it to follow repository conventions: - Fix/suppress analysis warnings - Some via `dart fix`, some manual - Add repo-level metadata - Update license check command to recognize this package - Add a temporary code-excerpt exclusion - Update pubspec.yaml metadata - Bump version to 2.0.1 to release the changes `mustache_template` was itself a fork by a Flutter team member of the third-party `mustache` package, so the import is into `third_party/packages/`, updating the repo license check to recognize the license of this package. The original code is quite old, and as a result still used a lot of implicit dynamic typing. Some of that that has been addressed in this import, but the trickier aspects have been left for future work, as converting from implicit dynamic typing to specified types has the potential for runtime regressions. (It's possible that even the more minor changes made here will cause regressions that will need fast-follow, but all the tests still pass, and the manual `test/all.dart` tests do not have any failures that were not present before making changes to the imported code). Issues filed for future follow-up work: https://github.com/flutter/flutter/issues/174721 https://github.com/flutter/flutter/issues/174722 https://github.com/flutter/flutter/issues/174742 ## Pre-Review Checklist [^1]: Regular contributors who have demonstrated familiarity with the repository guidelines only need to comment if the PR is not auto-exempted by repo tooling.	8 个月前
analysis_options.yaml	Remove `no_adjacent_strings_in_list` from enabled lint rules. (#7878) `no_adjacent_strings_in_list` conflicts with another rule, `prefer_adjacent_string_concatenation`. I suggest removing the former. See https://github.com/dart-lang/sdk/issues/59041 `prefer_adjacent_string_concatenation` is a style-oriented rule, but it is in the package:lints recommended set. So... it is recommended. `no_adjacent_strings_in_list` is an error-preventing lint rule, but it's usefulness is waning, as the [new style of the Dart formatter will always split adjacent strings into new lines](https://github.com/dart-lang/sdk/issues/59041). We are marking these two lint rules as incompatible. If the fix in this PR is not desired, there are two other options: * Remove `prefer_adjacent_string_concatenation` from the enabled lint rules. * Insert an `# ignore:` comment in the top-level analysis options file, and an `# ignore: included_file_warning` comment in any files that include the top-level one.	5 个月前
customer_testing.bat	remove temporary flag after migration (#3498) remove temporary flag after migration	3 年前
customer_testing.sh	Remove "All right reserved" from all files (#10066) Per guidance from legal on current preferred practice, remove "All rights reserved" from all LICENSE files and header blocks, and update the repo tool check accordingly.	7 个月前

Flutter Packages

This repo is a companion repo to the main flutter repo. It contains the source code for Flutter's first-party packages (i.e., packages developed by the core Flutter team). Check the packages directory to see all packages.

These packages are also available on pub.

Issues

Please file any issues, bugs, or feature requests in the main flutter repo. Issues pertaining to this repository are labeled "package".

Contributing

If you wish to contribute a new package to the Flutter ecosystem, please see the documentation for developing packages. You can store your package source code in any GitHub repository (the present repo is only intended for packages developed by the core Flutter team). Once your package is ready you can publish to the pub repository.

If you wish to contribute a change to any of the existing packages in this repo, please review our contribution guide, and send a pull request.

Packages

These are the packages hosted in this repository:

Package	Pub	Points	Usage	Issues	Pull requests
animations
camera
cross_file
cupertino_icons
espresso
extension_google_sign_in_as_googleapis_auth
file_selector
flutter_lints
flutter_plugin_android_lifecycle
flutter_svg
flutter_svg_test
flutter_template_images
go_router
go_router_builder
google_adsense
google_fonts
google_maps_flutter
google_sign_in
image_picker
interactive_media_ads
in_app_purchase
local_auth
metrics_center
multicast_dns
path_parsing
path_provider
pigeon
pointer_interceptor
plugin_platform_interface
quick_actions
google_identity_services_web
mustache_template
rfw
shared_preferences
standard_message_codec
two_dimensional_scrollables
url_launcher
vector_graphics
vector_graphics_codec
vector_graphics_compiler
video_player
web_benchmarks
webview_flutter
xdg_directories