Andrew Worcester

@benmvp sorry for the delay, I'm ready over this and will respond soon.

ok, I think I have an idea of how we can do this and introduce a little less mental overhead. ### New `plop.apiMethods()` - `plop.setGeneratorDefaults(configObject)`: As you described above, a...

yeah, I could see these `get` methods being added for all of the main data types (generators, helpers, partials, actionTypes, and templateRenderers). Definitely saves a step when you need to...

your modified example looks good, but (in reality) the eventual usage would probably look more like... ``` javascript export default (plop) => { plop.load('plop-ejs'); plop.setGenerator('name', { templateRenderer: 'ejs', description: 'A...

great, thanks!

@benmvp hmmmm, I'll look into this in more detail today. I actually had a moment there where something inside me said "that was almost... too easy". 😐

it's still on "my list" but unfortunately, my calendar blew up at work and home so I haven't been able to find much time. I suppose we would need to...

yeah, I would just look at PR plopjs/node-plop#58. It was put up a long time ago and I always meant to merge it, but I wanted to see if I...

yeah, it look like we need to add a case in the checkbox logic for passing "no value". we split the input value on `,`, so I think it would...

the prompt bypass functionality... where you can tack on the answers to prompts as part of the initial command, basically pre-answers prompts and removes them from the chain. Whatever prompts...