You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sassdown is great however, if I have a regular css comment (/* ... */) in either a sass partial file I've created or a 3rd party sass partial I'm importing, sassdown assumes this is a module for the styleguide.
The two should be independent of each other with regular css comments being ignored by sassdown.
The text was updated successfully, but these errors were encountered:
If regular (block-level) CSS comments are ignored by Sassdown, this would make it significantly more difficult to author longer and more detailed descriptions, examples, and notes in partials.
Two things:
Don't forget that you can define your own opening and closing comment syntax for Sassdown to parse. See the Grunt options in the README.
You can also use the glob array in files to exclude certain filenames or directories, if there is code you wish to ignore.
Unless either of the two solutions presents a problem, I'm closing this ticket.
Sassdown is great however, if I have a regular css comment (/* ... */) in either a sass partial file I've created or a 3rd party sass partial I'm importing, sassdown assumes this is a module for the styleguide.
The two should be independent of each other with regular css comments being ignored by sassdown.
The text was updated successfully, but these errors were encountered: