remove flutter_test quiver dep, use fake_async and clock instead#54125
remove flutter_test quiver dep, use fake_async and clock instead#54125jakemac53 merged 5 commits intoflutter:masterfrom
Conversation
|
It looks like this pull request may not have tests. Please make sure to add tests before merging. If you need an exemption to this rule, contact Hixie on the #hackers channel in Chat. Reviewers: Read the Tree Hygiene page and make sure this patch meets those guidelines before LGTMing. |
jonahwilliams
left a comment
There was a problem hiding this comment.
LGTM
Note for future readers. This will increase the number of packages that flutter_test depends on by 1. Each package is significantly smaller than quiver however, so it should be considered a net positive.
|
Correct it does increase the number of packages - I have filed an issue on quiver to also just export these packages instead of duplicating the code, so ultimately it maybe a reduction in dependencies of 1 if they did choose to do that. |
a3cff11 to
4dfddb4
Compare
|
Note that this is currently blocked on rolling the new fake_async internally which I am doing now |
|
Updated with design doc/migration plan as this did turn out to be breaking. Will rebase and fix conflicts once its ready to land. |
|
fly-by comment: I saw you wrote a migration guide linked in the PR description. We typically publish those on our website here to make them available to our users: https://github.com/flutter/website/tree/master/src/docs/release/breaking-changes |
|
Oh ok - I will go ahead and send a pr for it there, that gives a better opportunity for commenting on the wording of it etc as well 👍 |
|
This is the type of breaking change for which the affected audience is likely to be quite sophisticated and able to roll with the new API. The migration guide is great, and should be all the community needs. |
Description
Removes the
flutter_testdependency onquiver, instead using the more targetedclockandfake_asyncpackages.Related Issues
#53908
Tests
No changes to tests
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes (
[x]). This will ensure a smooth and quick review process.///).flutter analyze --flutter-repo) does not report any problems on my PR.Breaking Change
Did any tests fail when you ran them? Please read Handling breaking changes.