I think ember-watson is the right place to solve the problems you're describing.

Last I knew, the barrier to doing htmlbars rewriting was creating a whitespace-preserving AST printer. We actually already implement some of the transformations you'd want, they just happen at compile time now, and can't be easily printed back out as template files.

Fair enough, I'll close this and contribute to ember-watson.

Perhaps we can revisit this once it has more comprehensive coverage of depreciations? It would be nice to explicitly include new depreciations in ember-watson as part of the depreciation process, include links in the depreciation documentation and possibly include ember-watson in ember-cli

I don't think we will block new deprecations from being added on having automated upgrade tooling, but we definitely are blocking deprecations without an entry in the deprecation guide for the version in question. My goal would be to ensure that this guide has all the info required for someone to be able to add upgrade automation to ember-watson.

@rwjblue Sounds good, thanks

The first of many (hopefully): abuiles/ember-watson#87