History

Deletes files that should be ignored (#127984 )

Some files are supposed to ignore, but don't.

- **/windows/flutter/generated_plugins.cmake
- **/linux/flutter/generated_plugin_registrant.cc
- **/linux/flutter/generated_plugin_registrant.h
- **/linux/flutter/generated_plugins.cmake
- **/windows/flutter/generated_plugin_registrant.cc
- **/windows/flutter/generated_plugin_registrant.h
- **/ios/Runner/GeneratedPluginRegistrant.h
- **/ios/Runner/GeneratedPluginRegistrant.m

*List which issues are fixed by this PR. You must list at least one issue.*

*If you had to change anything in the [flutter/tests] repo, include a link to the migration guide as per the [breaking change policy].*

2023-06-29 19:45:22 +00:00

android

Revert "[integration_test] upgrade androidx test to 1.4.0" (#124644 )

2023-04-11 18:54:59 -07:00

ios

iOS info.plist template: make UIViewControllerBasedStatusBar to be true (#128970 )

2023-06-20 18:11:18 +00:00

lib

Remove "note that" in our documentation (as per style guide) (#120842 )

2023-02-17 22:27:33 +00:00

macos

Migrate Xcode projects last version checks to Xcode 14.3 (#125827 )

2023-05-02 00:06:33 +00:00

test

Add spaces after flow control statements (#126320 )

2023-05-15 11:07:30 +02:00

test_driver

Remove unnecessary null checks in dev/benchmarks (#118840 )

2023-01-20 04:04:11 +00:00

test_memory

Add bad scroller benchmark (#110362 )

2022-08-26 18:50:07 +00:00

windows

Deletes files that should be ignored (#127984 )

2023-06-29 19:45:22 +00:00

pubspec.yaml

flutter update-packages --force-upgrade (#128908 )

2023-06-15 18:17:09 +00:00

README.md

…

README.md

complex_layout

Scrolling benchmark

To run the scrolling benchmark on a device:

flutter drive --profile test_driver/scroll_perf.dart

Results should be in the file build/complex_layout_scroll_perf.timeline_summary.json.

More detailed logs should be in build/complex_layout_scroll_perf.timeline.json.

Startup benchmark

To measure startup time on a device:

flutter run --profile --trace-startup

The results should be in the logs.

Additional results should be in the file build/start_up_info.json.