flutter/bin/internal
Ian Hickson 29928a46ed
Support setting the elevation of disabled floating action buttons (#24728)
Previously, a disabled floating action button always had zero
elevation, which looks dumb.

This also fixes the issue whereby highlightElevation was not honoured
on floating action buttons.

This also fixes an issue I found during testing whereby setState was
being called during build when onHighlightChanged fired due to
onPressed becoming null while a gesture is ongoing (which triggers an
onTapCancel synchronously during build).
2019-01-15 15:06:29 -08:00
..
engine.merge_method Switch engine.merge_method back to squash (#24319) 2018-11-13 17:12:36 -08:00
engine.version fea645b80 update site to use SkFont for text fields (flutter/engine#7464) (#26536) 2019-01-14 14:14:48 -05:00
goldens.version Support setting the elevation of disabled floating action buttons (#24728) 2019-01-15 15:06:29 -08:00
gradle_wrapper.version Make artifacts URLs configurable. (#13380) 2017-12-07 16:30:23 +01:00
material_fonts.version Make artifacts URLs configurable. (#13380) 2017-12-07 16:30:23 +01:00
README.md Add engine merge method configuration (#23953) 2018-11-07 13:06:38 -08:00
update_dart_sdk.ps1 update_dart_sdk.ps1: Fall back to Invoke-WebRequest if BITS fails (#19873) 2018-07-27 14:29:20 -07:00
update_dart_sdk.sh Update links for China help (#25238) 2018-12-21 10:12:49 -08:00

Dart SDK dependency

The bin/internal/engine.version file controls which version of the Flutter engine to use. The file contains the commit hash of a commit in the https://github.com/flutter/engine repository. That hash must have successfully been compiled on https://build.chromium.org/p/client.flutter/ and had its artifacts (the binaries that run on Android and iOS, the compiler, etc) successfully uploaded to Google Cloud Storage.

The /bin/internal/engine.merge_method file controls how we merge a pull request created by the engine auto-roller. If it's squash, there's only one commit for a pull request no matter how many engine commits there are inside that pull request. If it's rebase, the number of commits in the framework is equal to the number of engine commits in the pull request. The latter method makes it easier to detect regressions but costs more test resources.