Add ability to use file exclusion patterns or glob expressions

[pascalduez]

On IRC @jsit asked whether SassDoc supports files exclusions patterns.
I kinda like the idea, and we could push things even further with supporting glob expressions ?
Since some major refactor will be engaged in file.js anyway. See #217 + upcoming issue.

But somehow it's raising some questions:
If you don't want files or items to show up in your docs, just don't document them...
Or use standard inline comments //.
One could also use a poster comment per file with an @private.

Does it makes sense ?
How would we implement this ?

[jsit]

I was thinking something in view.json (.sassdocrc) like:

"exclude": [
    "_vendors/some-library/**/*.scss"
]

If you don't want files or items to show up in your docs...

I was imagining this being useful when using third-party code that's also using SassDoc comments, but whose documentation you don't want ending up in your documentation.

[FWeinb]

For supporting glob parameters I would suggest node-glob.

[KittyGiraudel]

I did not consider this sooner because my Sass architecture is built in such way that all things that need to be documented lay down in the same folder (utils). Thus there is no need for exclusions.

But I think it makes sense in some way. I'd like something like this.

@SassDoc/owners You do understand this would mean having actual configuration in SassDoc itself, theme step aside (which would be fully supported yet, even if we don't use it at the moment). We would have needed it sooner or later anyway.

[FWeinb]

This must be in 2.0 because this will break the current api.

[KittyGiraudel]

Any reason so?

[FWeinb]

Currently SassDoc is taking a folder. So /path/to/folder would need to be /path/to/folder/**/*.scsswhen using globing.

[KittyGiraudel]

Can't we just add **/*.scss at the end of <src>?

[FWeinb]

Than we would need some logic to detect if a path is a glob-path or not.

[KittyGiraudel]

Okay. Let's keep it for 2.0.