In this version, Flutter can report an error if compilation during testing times out. In the v0.2.2, v0.2.3 contains updating engine version.
We didn't write any post about v0.2.1, v0.2.2, v0.2.3 before. We will say features in these versions. So, Flutter have some new commits in these versions. v0.2.2, v0.2.3 about the engine version. These versions changed engine version. Let's look changes in these versions.
The updated 2 Flutter engine versions has 25 commits and 38 files changes. You can look commits and changes by clicking this page.
#15265 updated ThemeData to use the primary color of a MaterialColor instead of unconditionally using the 500 shade for light themes. The color values remain unchanged. Before
expect(widget.color, Colors.blue.shade500) // primary color
expect(widget.color, Colors.blue) // primary color
#15303 updated the showDialog function to take a builder and deprecated the widget parameter. Before
showDialog(context: context, child: new Text('hello'))
showDialog(context: context, builder: (BuildContext context) => new Text('hello'))
#15484 changed the meaning of the TextFormField initialValue constructor parameter.
The TextFormField initialValue parameter no longer unconditionally initializes the text property of its TextEditingController. If you create a TextFormField and provide a controller, the initialValue must be null, which is now the default. If you're providing a controller you can specify it's initial text value with the TextEditingController text property. Before
new TextFormField( initialValue: 'Hello World', controller: _myTextEditingController, );
new TextFormField( controller: _myTextEditingController ..text = 'Hello World', ) // Or more typically: _myTextEditingController = new TextEditingController( text: 'Hello World', ); new TextFormField( controller: _myTextEditingController, );
#15537 removed SemanticsSortOrder. From now on traversal sorting is done among sibling nodes only. More details available in the announcement.
flutter/flutter#15416 removed package:http from Flutter and replaced all usages with the dart:io HttpClient. If you use package:http you must add it as a dependency in your pubspec.yaml to continue using it. createHttpClient was also removed after being marked deprecated. To change how the framework creates http clients, you can use HttpOverrides from dart:io to provide your own createHttpClient callback globally or per zone. More details are available in the announcement.