@requires Ruby/vendor items

[pascalduez]

We should find a way to @requires functions declared in Ruby, while extending Sass::Script::Functions.
Right now it logs a message, which is great, but the function don't get printed in the requires.

[pascalduez]

Which makes me think, it would be also be neat to be able to @requires third parties dependencies:
@requires compass::sprites::sprite-position
@requires SassyList::reverse
Something in that fashion.

[KittyGiraudel]

What about @requires {native} item?

[pascalduez]

So @requires {native} item for the project own functions.
And maybe @requires {vendor} SassyLists.reverse for third parties ?
Or @requires {vendor} reverse from SassyLists

[FWeinb]

Why not include the link to the documentation of the third party:
@requires {vendor} SassyList.reverse (http://sassylists.com/documentation.html#sl-reverse)

[pascalduez]

Why not include the link to the documentation of the third party:

Even better !

[KittyGiraudel]

Why not include the link to the documentation of the third party:

Because the third party may not have a documentation.

[FWeinb]

But if it has it would be great. De should at least allow it.

[KittyGiraudel]

Yep.

[aaronlademann-wf]

I think the syntax for the vendor stuff should be linked to how it is imported... This may allow for the {context} specifier to remain consistent with non-vendor/lib requirements, specifying function|mixin|variable.

For instance (using dot-notation)...

@import "SassyLists";
@import "sassy-maps";

/**
 * @requires {function} SassyLists.function-name
 * @requires {mixin} sassy-maps.mixin-name
 */

Or (using slash/dir notation)...

@import "SassyLists";
@import "sassy-maps";

/**
 * @requires {function} SassyLists/function-name
 * @requires {mixin} sassy-maps/mixin-name
 */

[aaronlademann-wf]

Also - I don't think this should be limited to "Ruby" libraries... but rather anything that is being required and imported (vendor Sass libraries, for instance).