Tasks

[nporteschaikin]

Here's my idea for "tasks" (e.g. generators):

• An optional folder in a template called tasks.

• On init, if the folder exists, drop a .sproutrc file in the target with the name of the template.

• The tasks folder contains js files (the name of the task == the filename). Each JS file exports a function with an options argument (passed as separate args to the CLI) and a utils argument:

  module.exports = function (options, utils) {
    // do some ish
  }

• To run a task, run sprout run <task> in the target directory:

  $ sprout run aTask

  sprout finds the template by the name in .sproutrc (if it can't be found, lists all your templates with readline/inquirer and lets you select/update .sproutrc).

[nporteschaikin]

cc/ @kylemac @joshrowley

[joshrowley]

sounds good to me. why .sproutrc and not just .sprout. also, how do you envision data being stored in that dotfile, is it just the template name, should we also give the template the ability to store other info in there?

[nporteschaikin]

@joshrowley:

• I like appending rc to make it clear it's a configuration file.
• I think we may want to eventually store more information in there. I'll probably store it as json; for now, it'll only have a name key.

[kylemac]

to clarify, tasks is the same thing as our generators concept, right? if so, i'm not sure i like the name tasks. also, we would need to pass options to the function as well. like if i ran $ sprout run model user

[nporteschaikin]

Let's call 'em generators. And yes, each task should be passed an args argument. Updated above.

[kylemac]

is there any other info that we need accessed by the generators, like target?

[nporteschaikin]

@kylemac utils will give it everything it needs, like it does with the hooks.

[kylemac]

👍