search

francescomari / grunt-sling-content

Deploy local content to a Sling instance
MIT License
6 stars 4 forks source link

Change npm package name from grunt-sling-content to grunt-sling #10

Closed bpauli closed 11 years ago

bpauli commented 11 years ago

If #9 will be implemented as extra task we will have two grunt task in one npm package

  1. grunt-sling-content
  2. grunt-sling-import

I would recommend to rename the npm package from grung-sling-content just to grung-sling.

francescomari commented 11 years ago

I think that grunt-sling-content is a good name for a module which uses the Sling POST servlet to handle content. I would better rename the existing sling-content task to slingPost and name the new task slingImport.

The camel-case notation will be useful at configuration time in the Gruntfile, I find writing a name in quotes is really annoying. But, of course, I realized too late.

bpauli commented 11 years ago

Yes, that makes sense. Just do it!

honstar commented 11 years ago

+1 for slingPost and slingImport.

francescomari commented 11 years ago

Reopening the issue, it will close when the change will be applied.

francescomari commented 11 years ago

@bpauli thanks for the contribution.