Allowing an array of plugins instead of objects

[jeffjewiss]

Allowing an array of plugins instead of objects

[jeffjewiss]

I can't remember the specific reason that I set it up that way originally. I think it had to do with the timing of when plugins were initialized.

The merging of plugin options with global options is the main reason to have the plugin and it's options separate, but I believe there are only a few plugins that really take advantage of this. autoprefixer is an example since the browserlist config can be passed in when using this package as part of ember-cli-postcss.

I think your proposal is sound and would work well. If users of this plugin want to specify plugins with the array format and pass the options directly to the plugin function, then they'll need to manage the options themselves anyway.

If you have time to put together a PR I'd really appreciate it and I'm open to supporting both methods.

[alexlafroscia]

Sweet! I'll do that then. I have the test written for the method I suggested, but wanted to make sure you're cool with both methods before writing the code and asking you to support two methods.

[jeffjewiss]

Thanks for checking, sounds good!