文件最后提交记录最后更新时间
Roll pub packages (#155846) This PR was generated by flutter update-packages --force-upgrade.1 年前
Reverts "Roll pub packages (#156440)" (#156473) Reverts: flutter/flutter#156440 Initiated by: zanderso Reason for reverting: Failing in post submit with ``` [2024-10-08 18:00:22.743647] [STDOUT] stdout: [!] CocoaPods could not find compatible versions for pod "Google-Mobile-Ads-SDK": [2024-10-08 18:00:22.743695] [STDOUT] stdout: In Podfile: [2024-10-08 18:00:22.743718] [STDOUT] stdout: google_mobile_ads (from .symlinks/plugins/google_mobile_ads/ios) was resolved t Original PR Author: flutter-pub-roller-bot Reviewed By: {fluttergithubbot} This change reverts the following previous change: This PR was generated by flutter update-packages --force-upgrade.1 年前
oh-3.27.4-dev分支回退模版和测试工程api版本为api12 Signed-off-by: liujiake <liujiake999@163.com> 9 个月前
[flutter_releases] Flutter beta 3.27.0-0.1.pre Framework Cherrypicks (#157268) Engine beta https://github.com/flutter/engine/commit/af0f0d559c8a87d912a20971bbd84afc80a54b0f https://chat.google.com/room/AAAA6RKcK2k/006XviXYyII/oKZa94exHE4?cls=10 Cherry pick of [7b0b03b](https://github.com/flutter/flutter/commit/7b0b03bc0df8eecfe2503aa2ea36958fc678e3ba)1 年前
Reverts "Roll pub packages (#156440)" (#156473) Reverts: flutter/flutter#156440 Initiated by: zanderso Reason for reverting: Failing in post submit with ``` [2024-10-08 18:00:22.743647] [STDOUT] stdout: [!] CocoaPods could not find compatible versions for pod "Google-Mobile-Ads-SDK": [2024-10-08 18:00:22.743695] [STDOUT] stdout: In Podfile: [2024-10-08 18:00:22.743718] [STDOUT] stdout: google_mobile_ads (from .symlinks/plugins/google_mobile_ads/ios) was resolved t Original PR Author: flutter-pub-roller-bot Reviewed By: {fluttergithubbot} This change reverts the following previous change: This PR was generated by flutter update-packages --force-upgrade.1 年前
Reverts "Roll pub packages (#156440)" (#156473) Reverts: flutter/flutter#156440 Initiated by: zanderso Reason for reverting: Failing in post submit with ``` [2024-10-08 18:00:22.743647] [STDOUT] stdout: [!] CocoaPods could not find compatible versions for pod "Google-Mobile-Ads-SDK": [2024-10-08 18:00:22.743695] [STDOUT] stdout: In Podfile: [2024-10-08 18:00:22.743718] [STDOUT] stdout: google_mobile_ads (from .symlinks/plugins/google_mobile_ads/ios) was resolved t Original PR Author: flutter-pub-roller-bot Reviewed By: {fluttergithubbot} This change reverts the following previous change: This PR was generated by flutter update-packages --force-upgrade.1 年前
Merge commit 'a241f514edfb61ca721a0ffdbd4de05bd82e007f' into oh-3.27.4-dev 1 年前
Update API docs footer (#150347) Update API docs footer with a cookie banner (go/cookiebanner) using the glue banner (go/glue-cookiebar) ## Pre-launch Checklist - [x] I read the [Contributor Guide] and followed the process outlined there for submitting PRs. - [x] I read the [Tree Hygiene] wiki page, which explains my responsibilities. - [x] I read and followed the [Flutter Style Guide], including [Features we expect every widget to implement]. - [x] I signed the [CLA]. - [x] I listed at least one issue that this PR fixes in the description above. - [x] I updated/added relevant documentation (doc comments with ///). - [x] I added new tests to check the change I am making, or this PR is [test-exempt]. - [x] I followed the [breaking change policy] and added [Data Driven Fixes] where supported. - [x] All existing and new tests are passing. If you need help, consider asking for advice on the #hackers-new channel on [Discord]. <!-- Links --> [Contributor Guide]: https://github.com/flutter/flutter/wiki/Tree-hygiene#overview [Tree Hygiene]: https://github.com/flutter/flutter/wiki/Tree-hygiene [test-exempt]: https://github.com/flutter/flutter/wiki/Tree-hygiene#tests [Flutter Style Guide]: https://github.com/flutter/flutter/wiki/Style-guide-for-Flutter-repo [Features we expect every widget to implement]: https://github.com/flutter/flutter/wiki/Style-guide-for-Flutter-repo#features-we-expect-every-widget-to-implement [CLA]: https://cla.developers.google.com/ [flutter/tests]: https://github.com/flutter/tests [breaking change policy]: https://github.com/flutter/flutter/wiki/Tree-hygiene#handling-breaking-changes [Discord]: https://github.com/flutter/flutter/wiki/Chat [Data Driven Fixes]: https://github.com/flutter/flutter/wiki/Data-driven-Fixes1 年前
Reverts "Roll pub packages (#156440)" (#156473) Reverts: flutter/flutter#156440 Initiated by: zanderso Reason for reverting: Failing in post submit with ``` [2024-10-08 18:00:22.743647] [STDOUT] stdout: [!] CocoaPods could not find compatible versions for pod "Google-Mobile-Ads-SDK": [2024-10-08 18:00:22.743695] [STDOUT] stdout: In Podfile: [2024-10-08 18:00:22.743718] [STDOUT] stdout: google_mobile_ads (from .symlinks/plugins/google_mobile_ads/ios) was resolved t Original PR Author: flutter-pub-roller-bot Reviewed By: {fluttergithubbot} This change reverts the following previous change: This PR was generated by flutter update-packages --force-upgrade.1 年前
Merge commit 'a241f514edfb61ca721a0ffdbd4de05bd82e007f' into oh-3.27.4-dev 1 年前
pattern-matching refactor (#154753) This pull request aims to improve code readability, based on feedback gathered in a recent design doc. <br> There are two factors that hugely impact how easy it is to understand a piece of code: **verbosity** and **complexity**. Reducing **verbosity** is important, because boilerplate makes a project more difficult to navigate. It also has a tendency to make one's eyes gloss over, and subtle typos/bugs become more likely to slip through. Reducing **complexity** makes the code more accessible to more people. This is especially important for open-source projects like Flutter, where the code is read by those who make contributions, as well as others who read through source code as they debug their own projects. <hr> <br> The following examples show how pattern-matching might affect these two factors: <details> <summary><h3>Example 1 (GOOD)</h3> [click to expand]</summary> ```dart if (ancestor case InheritedElement(:final InheritedTheme widget)) { themes.add(widget); } ``` Without using patterns, this might expand to ```dart if (ancestor is InheritedElement) { final InheritedWidget widget = ancestor.widget; if (widget is InheritedTheme) { themes.add(widget); } } ``` Had ancestor been a non-local variable, it would need to be "converted" as well: ```dart final Element ancestor = this.ancestor; if (ancestor is InheritedElement) { final InheritedWidget inheritedWidget = ancestor.widget; if (widget is InheritedTheme) { themes.add(theme); } } ``` </details> <details> <summary><h3>Example 2 (BAD) </h3> [click to expand]</summary> ```dart if (widget case PreferredSizeWidget(preferredSize: Size(:final double height))) { return height; } ``` Assuming widget is a non-local variable, this would expand to: ```dart final Widget widget = this.widget; if (widget is PreferredSizeWidget) { return widget.preferredSize.height; } ``` <br> </details> In both of the examples above, an if-case statement simultaneously verifies that an object meets the specified criteria and performs a variable assignment accordingly. But there are some differences: Example 2 uses a more deeply-nested pattern than Example 1 but makes fewer useful checks. **Example 1:** - checks that ancestor is an InheritedElement - checks that the inherited element's widget is an InheritedTheme **Example 2:** - checks that widget is a PreferredSizeWidget (every PreferredSizeWidget has a size field, and every Size has a height field) <br> <hr> I feel hesitant to try presenting a set of cut-and-dry rules as to which scenarios should/shouldn't use pattern-matching, since there are an abundance of different types of patterns, and an abundance of different places where they might be used. But hopefully the conversations we've had recently will help us converge toward a common intuition of how pattern-matching can best be utilized for improved readability. <br><br> - resolves https://github.com/flutter/flutter/issues/152313 - Design Doc: [flutter.dev/go/dart-patterns](https://flutter.dev/go/dart-patterns)1 年前
Enable private field promotion for dev (#134480) New feature in upcoming Dart 3.2. See https://github.com/dart-lang/language/issues/2020. Feature is enabled by bumping the min SDK version to 3.2. Part of https://github.com/flutter/flutter/issues/134476.2 年前
Reverts "Roll pub packages (#156440)" (#156473) Reverts: flutter/flutter#156440 Initiated by: zanderso Reason for reverting: Failing in post submit with ``` [2024-10-08 18:00:22.743647] [STDOUT] stdout: [!] CocoaPods could not find compatible versions for pod "Google-Mobile-Ads-SDK": [2024-10-08 18:00:22.743695] [STDOUT] stdout: In Podfile: [2024-10-08 18:00:22.743718] [STDOUT] stdout: google_mobile_ads (from .symlinks/plugins/google_mobile_ads/ios) was resolved t Original PR Author: flutter-pub-roller-bot Reviewed By: {fluttergithubbot} This change reverts the following previous change: This PR was generated by flutter update-packages --force-upgrade.1 年前
Merge commit 'a241f514edfb61ca721a0ffdbd4de05bd82e007f' into oh-3.27.4-dev 1 年前
Roll pub packages (#155846) This PR was generated by flutter update-packages --force-upgrade.1 年前
Migrate to .ci.yaml (#82960) 4 年前
Enable more lints (#91642) 4 年前
README.md

This directory contains tools and resources that the Flutter team uses during the development of the framework. The tools in this directory should not be necessary for developing Flutter applications, though of course, they may be interesting if you are curious.

The tests in this directory are run in the framework_tests_misc-* shards.