In v3.0.0, the value setter was replaced by valueListenable. This is a breaking change that requires a non-trivial migration for existing projects. Furthermore, this move deviates from the standard value/onChanged pattern found in Flutter’s native DropdownButtonFormField.
Could you provide some insight into the reasoning behind this change? Specifically, why was this implemented as a mandatory change rather than an optional alternative?
Small note: often in Flutter this kind of property is called controller I think.
In v3.0.0, the value setter was replaced by
valueListenable. This is a breaking change that requires a non-trivial migration for existing projects. Furthermore, this move deviates from the standard value/onChanged pattern found in Flutter’s native DropdownButtonFormField.Could you provide some insight into the reasoning behind this change? Specifically, why was this implemented as a mandatory change rather than an optional alternative?
Small note: often in Flutter this kind of property is called
controllerI think.