As the Flutter team works towards deprecating the 'package:flutter/material.dart' import now that 'package:material_ui' and 'package:cupertino_ui' are available, we need to start looking to decouple ourselves from the old import, and wherever possible from either design pattern.
Luckily, we have little dependency on Material already.
It's important to note that we currently support back to Flutter 3.27 in both the library and example app. Updating to use the newer separated libraries requires Flutter 3.44.
Ideally, we keep the library as backward-supporting as possible. The example app could be updated to use Flutter 3.44 or above, but we currently build the example app in our CI/CD pipelines to ensure that the library can be build on Flutter 3.27. It's possible this is OK if we can rely on the tests to still prove support for the minimum supported version.
Our dependencies lie in the following:
- Unnecessary imports of 'material.dart' instead of 'widgets.dart' or 'dart:ui'
- The attribution widgets
- Tests and benchmarks
- The example project
As the Flutter team works towards deprecating the 'package:flutter/material.dart' import now that 'package:material_ui' and 'package:cupertino_ui' are available, we need to start looking to decouple ourselves from the old import, and wherever possible from either design pattern.
Luckily, we have little dependency on Material already.
It's important to note that we currently support back to Flutter 3.27 in both the library and example app. Updating to use the newer separated libraries requires Flutter 3.44.
Ideally, we keep the library as backward-supporting as possible. The example app could be updated to use Flutter 3.44 or above, but we currently build the example app in our CI/CD pipelines to ensure that the library can be build on Flutter 3.27. It's possible this is OK if we can rely on the tests to still prove support for the minimum supported version.
Our dependencies lie in the following: