Potential for collisions in plugin options

[necolas]

There's no documentation about passing options into plugins (e.g., postcss-custom-properties) but it looks like the options are passed to every plugin. That means postcss and all the plugins share the same level of the options and there's a chance for collisions if any of them use properties with the same name.

Maybe make it possible to set the value of a feature to be an options object?

[MoOx]

I've played a dangerous game indeed because I wanted to make a simple api.
For now all plugins have no conflict (I've been careful about that) & I always try to make name clear enough to avoid that.
But if we add the ability to add other plugins, this can be too dangerous.
Adding options for each feature can be nice & safe, but can be verbose :/
And for example if you have a preserve option for several plugins, you can just pass it once.

Not sure what is the best. Mixing both & merging for each plugins usage ?

[necolas]

Maybe keep it as-is then until there is an actual problem.

Not sure about supporting the ability to add other plugins - then it starts to turn into a wrapper over postcss. If people need extra stuff you could recommend that they use the same plugins individually in their own custom processing pipeline. Being clearly aligned to CSS draft specs is a good and simple identity, and the tool has that kind of name too :).