Since DualTransitionBuilder was introduced to flutter/flutter: #58686, this can result in a naming conflict for the animations package, since the animations package also contains an identical DualTransitionBuilder.
We should have the animations package use its own copy of the widget until DualTransitionBuilder reaches the stable branch. Then, we can safely remove the copy of DualTransitionBuilder in the animations package.
Since DualTransitionBuilder was introduced to
flutter/flutter: #58686, this can result in a naming conflict for theanimationspackage, since theanimationspackage also contains an identicalDualTransitionBuilder.We should have the
animationspackage use its own copy of the widget until DualTransitionBuilder reaches thestablebranch. Then, we can safely remove the copy of DualTransitionBuilder in the animations package.