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
Expand deprecation policy to package:flutter_test #122323
Comments
Is this appropriate place to raise issues with depreciation of methods and classes (in the flutter_test package) that are still needed because no equivalent method or class exists? |
Definitely! I think all of the listed APIs have migration paths, but if we are missing one we certainly would love to know! |
If we are extending to |
Great question! The long term goal is to expand the policy to cover all packages in flutter/flutter, and maybe even We're just doing this at a considerate pace since it means more potential breaking changes for developers. |
@Piinks I added a link to a ticket for adding dart fix support to the description. I plan on starting on it in the next couple weeks, hopefully early next week. |
* Adds fixes for the first round of deprecations listed in flutter#122323 * Adds tests for all new fixes * Adds a note for the `runTest(timeout)` deprecations to prevent them from being removed before `integration_test` also has `dart fix` support
Closing this as we are about to proceed with the next batch of deprecations, including flutter_test. Follow along in #127042 |
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of |
This is the tracking issue for the proposal to expand the deprecation policy to package:flutter_test
When first introduced, we decided to first focus the application of the deprecation policy on just the flutter package. During that time we worked on the process and gathered feedback from users. This process has become pretty stable, and so we are looking to expand it to other packages, with the first being flutter_test.
This will involve:
dart fix
capabilities toflutter_test
#123154If we were to do this after the next release (not the current round that completed with #119580 but the next round), these would be up for removal:
cc @goderbauer @pdblasi-google
The text was updated successfully, but these errors were encountered: