Common API across all Transforms

[RobLoach]

There has been the adoption of options.plugins in a couple of the transforms, which allows the loading of additional functionality. What other standards could we introduce?

Thoughts on some of the following?

• options.partials - Associative array of partial name -> fn representing available partials
• options.includePaths - Array of paths to search when including files
• options.filename - Possible filename for the template location
• options.plugins - An array of strings (become require'd) or objects representing the plugins to use
• options.filters - An array of strings (become require'd) or functions representing filters to use

Others?

[tunnckoCore]

options.includes seems better to me, others :+1:

[RobLoach]

options.includes isn't really explicit in definition. It could be an array of locals, or even partials. It's not really explicit with what it actually means. I was following the following definition: https://github.com/sass/node-sass#includepaths