Considering renaming task `emberTemplates` about grunt-ember-templates HOT 4 CLOSED

+1 even though I don't use this project or grunt for major projects. It is important to keep naming consistent across the ecosystem. How would you feel is someone was naming their files like: require "FooBarBaz/qux" in Ruby? You'd probably be upset (I'd know I would be).

from grunt-ember-templates.

@twinturbo completely agree 👍

I'm pretty set on the rename, just hung up a bit on the versioning. I'm going to see if I can essentially alias both tasks (by registering both) and then phase out ember_templates after 0.4.

from grunt-ember-templates.

Makes sense. Version bump + alias I agree with. You're not at 1.0.0 so you
essentially do whatever you want as well :D

On Wed, May 22, 2013 at 9:49 PM, Dan Gebhardt [email protected]:

@twinturbo https://github.com/twinturbo completely agree [image: 👍]

I'm pretty set on the rename, just hung up a bit on the versioning. I'm
going to see if I can essentially alias both tasks (by registering both)
and then phase out ember_templates after 0.4.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/27#issuecomment-18303269
.

from grunt-ember-templates.

The deed is done. I've renamed the task to emberTemplates and deprecated ember_templates in 0.4.7.

from grunt-ember-templates.