Use standard Grunt "options" object. about grunt-saucelabs HOT 5 CLOSED

@cowboy This was one of the Grunt 0.4.0 things that I had been holding off from doing. Most grunt multi-tasks are file based. This task however requires URL and hence, src or dest options in a task may not make sense. With the options object, the task will end up looking something like

'saucelabs-qunit' : {
   task1 : {
       options: { 
            urls : [] <= URLs are like files, so they don't belong to the options object there. 
            browser: [], timeout : 10, // and more properties......
       } ,
       url : [] /// <= I would prefer to use this, since URLs are similar to files.
  },
   task2: {
       options: { 
            browser: [], timeout : 10, // and more properties......
    },
   options : {
       url : [] // <= URL is NOT a task level option, so it should not be inside the options object. 
   }
}

All of the options will have to be specified under either the task-level options object, or target-level options.
Basically, I would like URLs to available as task1.url and not task1.options.url.

Are there any other multi-task examples that rely are not file-centric where URLs are specified in a different manner ?

from grunt-saucelabs.

Had a good conversation on this topic with @shama at on IRC #grunt. Given that the tasks that this plugin exposes are very similar to qunit, it makes sense have the input arguments exactly like it would be for qunit. Note that this will be a breaking change and will update the version according to https://github.com/dominictarr/semver-ftw#major-breaking-changes

from grunt-saucelabs.

Fixed in 4c6eca6

from grunt-saucelabs.

👍

from grunt-saucelabs.

Thanks!!

from grunt-saucelabs.