-
Notifications
You must be signed in to change notification settings - Fork 4
Use @options (not @data) per Grunt guidelines #2
Conversation
Hehe, I got those guidelines into the readme because of their use of @DaTa and then I forgot to update this module. Nice On Sun, Nov 10, 2013 at 3:57 PM, Jason Karns notifications@github.com
|
Fair warning, this isn't backwards compatible. Any task configuration already using the old style won't get picked up correctly. |
I tried to tie this PR to #1, but apparently you can only submit PRs to issues created by you. |
Ah. We could make this BC easily enough On Sun, Nov 10, 2013 at 4:00 PM, Jason Karns notifications@github.com
|
Now backwards compatible. (and warns if using the old style config) |
👍 |
No longer be at the mercy of how minijasminenode handles duplicate files in `specs` option.
cleaned up the commits and plucked out the unrelated stuff. ready to merge |
Merged on faith |
To get target > task > default option merging out of the box, you have to
use
options
when configuring; as opposed to putting the settings directlyon the target. Then, within the task, use
this.options([defaults])
.