Implement tooling for migrating code away from deprecated Dart 1.0 constant names

As step 2 of the wave 1 core library changes, we need to remove the old deprecated constant names. To make this feasible, we should have a migration script that can be run as part of the flutter upgrade process to port code over to the new constant names.

Tracking issue for removing the deprecated names is #31813.

Tracking issue for the overall core lib migration is #31812.

Author: Fantashit

1 thought on “Implement tooling for migrating code away from deprecated Dart 1.0 constant names

  1. I think for this, we should enhance the @deprecated annotation to more easily support automated refactorings. There are some deprecations that we could easily tool, like a rename, if the deprecation annotation supported enough info to reference the new symbol.

Comments are closed.