Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Provide guidance about package:fake_async vs. FakeAsync from quiver #2300

Closed
jamesderlin opened this issue Feb 11, 2020 · 2 comments
Closed

Comments

@jamesderlin
Copy link
Contributor

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)?

@jamesderlin
Copy link
Contributor Author

CC @jakemac53 since flutter_test is moving in the opposite direction.

@jamesderlin
Copy link
Contributor Author

Closing in favor of google/quiver-dart#590.

@mosuem mosuem transferred this issue from dart-archive/fake_async Oct 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants