force vs no-prompt

[allanhortle]

There is a bit of a discrepancy between the cli and the grunt task so it took me a while to figure out how to disable override prompts. This should either use similar language or documented somewhere.

[pascalduez]

This is documented here: http://sassdoc.com/getting-started as of SassDoc/sassdoc.github.io#44

Note: options --sass-convert, --no-update-notifier and --no-prompt can also be set from the configuration file (set with --config) respectively with sass-convert, no-update-notifier and force.

Granted this is not straightforward enough. So we will update and clarify the docs.
Sorry for any inconvenience.

[jsit]

I don't see any of this documented on the sassdoc site anymore.

https://www.google.com/search?q=site%3Asassdoc.com+%22force%22

[pascalduez]

Hi @jsit,

starting from SassDoc 2.0 there's no force option anymore.

--no-prompt option no longer exists since SassDoc outputs its own folder (#302)

See https://github.com/SassDoc/sassdoc/blob/master/CHANGELOG.md#api-breaks-for-users
See SassDoc/sassdoc#302

So grunt-sassdoc >=2.0 is following SassDoc core behavior. Meaning there's only a src key necessary as in the examples. The docs files will be output in a sassdoc folder and that folder wiped without prompt.
If for some reasons you want to customize the output folder, you can do it with the dest option, either directly in the grunt task, or in a .sassdocrc if you have one.

[jsit]

@pascalduez, that's not the whole story -- I do still need to put force: true in my Gruntfile options if I'm specifying a dest. sassdoc 2.1.11

This is still absent from the documentation as far as I can tell; should it be added?