-
Notifications
You must be signed in to change notification settings - Fork 56
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Change behavior when no src
#347
Comments
Seconded. |
Like it. |
Oh! If we default to |
Why? |
Because it will document theme stylesheets with project stylesheets… and it feels odd |
C-style comments don't exist anymore. Project stylesheets won't contain any SassDoc comment. |
Oh right, it's okay if Though we might need some sort of default excludes, we don't want to documentize files under |
Agreed. |
This can't be merged for the today 2.0 release for sure. The problem is the current behavior is to read from It's possible to drop the current " Opinions on this @SassDoc/owners? We need to take an action on this before releasing 2.0. |
I suppose we can also consider dropping the idea of not passing |
Currently
sassdoc
executed as-is will try to read fromstdin
for SCSS input (that is, meant to be used likecat file | ... | sassdoc
.Though I don't expect this to be a common use and we might better default to documenting the CWD when SassDoc is executed without any
src
.The
-
is a standard convention to meanstdin/stdout
in Unix commands: http://tldp.org/LDP/abs/html/special-chars.html#DASHREF2The text was updated successfully, but these errors were encountered: