[Idea]: Pluggable Generators

[cmather]

I think the next big thing would be allowing plugin generators. I ran out of time for this cycle. But it would be cool if you could add a package, which added generators to the iron tool. It would involve things like:

Augmenting the idea of a 'generator' to a folder or a package that has a specific directory structure.
Adding generator template folders to the lookup search path for templates
Adding generator commands to the main command tool
This way people could design their own generators specific to their projects, or write plugins to help people generate different types of code.

cc @scott-mcpherson, @lirbank

[lirbank]

+1

Another thing I'd like to add is a way to have a personal default list of packages. Eg. I always remove insecure and autopublish and add the package-that check-if you-have-added-check()-to-all-methods and force-ssl and the browser content policy package and probable one or two more that I can't think of now.

This could be in the iron config file but that is per project and what I would like is more like a personal boilerplate for all my new projects.

Another thing I always do right away on new projects is to deny client side writes to the user.profile in the users collection. Something that not everyone wants but would be great to have in a personal boilerplate config as well. I could write this as a package and then with the package boilerplate include it in all my new projects.

Also have a custom way for configuring external login services that I am not sure can be in a package. So could be worth looking at if we should allow boilerplate code too.

I also have

[lirbank]

The personal boilerplate should also include a default iron config (eg coffee, CSS).

One idea I had was to use gist for the boilerplate config. Nice because people can share and get inspiration from one another's config. Bad because it will require Internet access.

[scottmcpherson]

These are all great ideas. Like @lirbank , even with the most simple demo apps, the first thing I always do is remove insecure and autopublish.

It might be nice to add a couple of properties to the create command, for the sake of this example we'll call them addPackages and removePackages. By default we could set addPackages: ['iron:router'] and just leave removePackages to an empty array.

And then maybe have the create command so that it could be overrode by a custom create command (created by the user).

Also, it would be nice to add a command onto iron that generates a pluggable boilerplate generator/command package.