You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's confusing that both package:fake_async and package:quiver both provide mostly-similar-but-not-the-same FakeAsync classes and that both are owned by the Dart team. I tried digging into the history, but it seems rather muddled (it looks like it was added to quiver first, and then a few months later the creator forked it into a separate package without clear explanation why). And while package:fake_async at some point was backwards compatible with quiver's, there's been some divergence.
Should package:fake_async guide people to use the quiver version instead (since that one seems to be maintained, is what Flutter uses, and has more inertia)?
The text was updated successfully, but these errors were encountered:
It's confusing that both
package:fake_async
andpackage:quiver
both provide mostly-similar-but-not-the-sameFakeAsync
classes and that both are owned by the Dart team. I tried digging into the history, but it seems rather muddled (it looks like it was added to quiver first, and then a few months later the creator forked it into a separate package without clear explanation why). And whilepackage:fake_async
at some point was backwards compatible with quiver's, there's been some divergence.Should
package:fake_async
guide people to use the quiver version instead (since that one seems to be maintained, is what Flutter uses, and has more inertia)?The text was updated successfully, but these errors were encountered: