indieisaconcept / grunt-context Goto Github PK

Change how contexts process overrides so that it uses the keys of context.options instead since some tasks may be an alias.

Eg: lint > jslint

grunt.registerHelper will be depreciated in grunt 0.4.

To see how helpers will be handled in the future (using standard npm require), check out the following links:

https://github.com/gruntjs/grunt-contrib-uglify/blob/master/tasks/uglify.js#L15 https://github.com/gruntjs/grunt-contrib-uglify/blob/master/tasks/lib/min.js

> grunt context:some.prop.test=1234

Implement support based on the discussion here: https://github.com/cowboy/grunt/issues/214

I'm posting this issue to let you know that we will be publishing Grunt 0.4 on Monday, February 18th.

If your plugin is not already Grunt 0.4 compatible, would you please consider updating it? For an overview of what's changed, please see our migration guide.

If you'd like to develop against the final version of Grunt before Monday, please specify "grunt": "0.4.0rc8" as a devDependency in your project. After Monday's release, you'll be able to use "grunt": "~0.4.0" to actually publish your plugin. If you depend on any plugins from the grunt-contrib series, please see our list of release candidates for compatible versions. All of these will be updated to final status when Grunt 0.4 is published.

Also, in an effort to reduce duplication of effort and fragmentation in the developer community, could you review the grunt-contrib series of plugins to see if any of your functionality overlaps significantly with them? Grunt-contrib is community maintained with 40+ contributors—we'd love to discuss any additions you'd like to make.

Finally, we're working on a new task format that doesn't depend on Grunt: it's called node-task. Once this is complete, there will be one more conversion, and then we'll never ask you to upgrade your plugins to support our changes again. Until that happens, thanks for bearing with us!

If you have any questions about how to proceed, please respond here, or join us in #grunt on irc.freenode.net.

Thanks, we really appreciate your work!

it conflicts with some of the grunt internals, and crashes grunt when you use a multitask with multiple targets overriden by your-plugin, alongside with some other task that uses templates (and not your plugin).
I have removed it and the problem disappeared. I think it would be wise to remove it.

I'm facing this error when I load grunt-context in my Gruntfile.js.

Loading "context.js" tasks...ERROR
>> TypeError: Object #<Object> has no method 'registerHelper'

Package.json

  "devDependencies": {
    "grunt": "~0.4.1",
    "grunt-s3": "~0.2.0-alpha",
    "grunt-contrib-uglify": "~0.2.0",
    "grunt-context": "~0.3.3"
  }

Allow propertyOverride to have a similar arguments signature as _.defaults or _.extend so that multiple overrides can be applied to destination.

Seems like a very useful plugin, would love to see it ported over :)

Allow context to run but not result in a task execution instead allow it to be used inside a task to change the context.

grunt.registerTask('default', 'context:dev jasmine lint');

Above would ensure that the context for each of the tasks run would be dev.

When refactoring for 0.3.1 forgot to restore this.args for command line functionality.

Use 0.3.0 until fixed.

Guys.

I miss a helper that tells me in which context my task is running (I built some tasks and I dont want some e-mails get sent on dev context).

Maybe I'll do a pull resquest for this.
Just leaving the issue in case somebody else is faster than me.