This issue was originally filed by jjinux...@google.com

This is in response to some problems I encountered when trying to update my code to libv2.

Go has gofix. We have a bunch of cleanups in the editor. They are very good, and I am very grateful to the editor team for them. However, perhaps we should do something a bit more industrial strength and foolproof. Perhaps we should be more like gofix.

Here's my suggestion:

 * Let's move the fixes out of the editor and into a tool called dartfix.

 * Every Dart project should have a pubspec.yaml that contains the version of the SDK that it is known to work with.

 * Whenever a breaking API change is made, the person making the API change is responsible for adding a fix to dartfix. The fix would use dart2dart to automatically fix the code.

 * Every time the user updates his SDK, the editor could run dartfix so that all of the correct Dart fixes would be applied.

 * dartfix would update some file to record that the fixes had been applied.

This would solve a few problems:

 * This would allow the libraries team to continue breaking APIs because the fixes would be applied to people's code automatically.

 * This would solve the problem of people not knowing when they need to apply cleanups and whether certain cleanups had already been applied.

 * This would move more code out of Java (I'm guessing it's in Java) and make the code reusable outside the editor.

 * This would put the engineer who breaks the API in charge of fixing people's code, which is probably more likely to be successful than the editor guys always trying to play catchup.