Tracking issue for promoting package:chrome_gen to package:chrome

[devoncarew]

This issue is to get comments and people's thoughts about making chrome_gen the preferred chrome API library. So, something like:

• rename the package chrome_gen to chrome, and rename the github repo or move the contents into the chrome repo
• rename the package chrome to something like chrome_old, and swizzle the github repo contents accordingly. This way people that still need to depend on the old repo can do so

I think this work is predicated on getting the old chrome tests running with the new chrome_gen package, so we maintain existing test coverage.

[adam-singer]

sgtm. Would like to see the unit testing generated apis and samples/examples integrated before doing the switch. @devoncarew do you have plans/time to extract the testing framework for spark so it can be shared? The other option is to use the existing testing configuration from chrome.dart.

[devoncarew]

do you have plans/time to extract the testing framework for spark so it can be shared

I do have plans to do that, but haven't really made any forward progress :) Pragmatically speaking, if you want to port the tests from chrome.dart in their current form, that would let us make progress w/o waiting on a new testing framework.

[adam-singer]

k, will get this started soon #47

[adam-singer]

This should be complete. The last steps should be

• updating the chrome_gen.dart README with deprecation and migration information
• publish a new package with updated README to pub
• migrate any bugs/issues to chrome.dart
• publish new chrome.dart on pub
• create blog post about update