Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Ben Briggs
    @ben-eb
    What happens if you drop this group name?
    Hm, I'm not sure if that is relevant.
    I'm not sure what is causing this issue, it might be a problem with your environment
    Jay Sitter
    @jsit
    Well, it helped me to figure out the problem anyway! It doesn't seem to be obeying my "dest" setting, so it's writing to a directory different from the one I was loading in my browser
    Ben Briggs
    @ben-eb
    My advice would be to try this config with a small test repo and try to reproduce the problem
    Jay Sitter
    @jsit
    And in the directory that it is writing to, the excludes are working. Whew!
    Ben Briggs
    @ben-eb
    Ah! Nice one! :)
    Jay Sitter
    @jsit
    Not sure why it's not obeying "dest" though -- is that deprecated?
    Ben Briggs
    @ben-eb
    I'm not sure actually, haven't used Grunt for a while :)
    Jay Sitter
    @jsit
    hm ok, that's my nexte problem then
    Thanks!
    Ben Briggs
    @ben-eb
    Good luck :)
    Jay Sitter
    @jsit
    Ok, got it; "dest" needs to be inside the "options" object
    Ben Briggs
    @ben-eb
    Right :+1:
    Jay Sitter
    @jsit
    Ok so I'm actually back to square one. It wasn't ignoring those files after all; the "General" section had just moved down to the bottom so I wasn't seeing it. :S
    Jay Sitter
    @jsit
    ben-eb: Surely this should work, right? http://pastebin.com/Dx8nZv1b
    Jay Sitter
    @jsit
    ben-eb: So, doing the negate syntax of '!../scss/vendor' is working when in Gruntfile, but seemingly no variation of that in the config.json file will properly do the exclusion.
    ben-eb: I also noticed that the exclusion only works if my src is '../scss/*'; before I had set it to '../scss'
    ben-eb: Er, scratch that last message; excluding works fine with src as just '../scss'
    Jay Sitter
    @jsit
    Ok so it turns out the glob syntax is just reeeeallly delicate and I wasn't doing it right. If my src is '../scss' and my exclude is 'vendor/**', everything works as expected.
    I need to brush up on glob, I guess. ¯_(ツ)_/¯
    Ben Briggs
    @ben-eb
    Sorry, I was eating :)
    Yep, globs can be like that
    Jay Sitter
    @jsit
    thanks
    What should I be using for src? "../scss/"? What's the difference between that and "../scss" or "../scss/" or "../scss//"?
    Ben Briggs
    @ben-eb
    I think gitter ate your code :)
    Try wrapping those with backticks
    Jay Sitter
    @jsit
    What should I be using for src? ../scss/*? What's the difference between that and ../scss or ../scss/** or ../scss/**/*?
    Thanks -- I'm logged in via IRC so I didn't see that problem
    Ben Briggs
    @ben-eb
    **/* will match any file in any directory, any levels deep, whereas * will match only files in that directory
    So src/* will match src/foo but not src/foo/bar whereas src/**/* will match src/foo/bar
    Vladimír Macháček
    @Machy8

    Hi! I am trying to use SassDoc for my css framework and I have a problem with the sass-converter. I have the example from the website (http://sassdoc.com/gulp/ Example adding support for Sass (indented syntax) files)

    var converter = require('sass-convert');
    var sassdoc = require('sassdoc');
    
    gulp.task('sassdoc', function () {
        return gulp.src('./src/**/*.sass')
            .pipe(converter({
                from: 'sass',
                to: 'scss',
            }))
            .pipe(sassdoc());
    });

    and when I run gulp it ends on 'starting sassdoc’. No output, no error.

    Vladimir:Grid Machy8$ gulp
    [13:20:35] Using gulpfile ~/Www/Grid/gulpfile.js
    [13:20:35] Starting 'sassdoc'

    But when I replace the .sass in the path by .scss it finishes normally. What I am doing wrong?

    Thanks for help!

    Vladimír Macháček
    @Machy8
    @ben-eb
    Ben Briggs
    @ben-eb
    @Machy8 Sorry, I don't use this tool
    Do you have ruby sass installed?
    Vladimír Macháček
    @Machy8

    Ok, thank you. I saw you are the one of those who answers here.

    Yes I have. Everything works fine except the sass-converter. It works only for the scss file type and no error is thrown.

    Ben Briggs
    @ben-eb
    Strange indeed. If I were you I would open an issue. :)
    Vladimír Macháček
    @Machy8
    Ok, thanks :D
    Jay Sitter
    @jsit
    What are the possible values for @param types?
    int, string, list...
    Severin
    @seveves
    what do you think about making the default theme colors configurable? F.e. sassdoc docs --configuration '{ ... themeColors: [ rgba(0,1,2,1), rgba(0,1,3,1) ... ] .. }'
    I like the default theme layout but want to change only the colors and currently the only way would be to clone the default theme and create my own.
    Severin
    @seveves
    if you are interested in such a feature then leave me a message. I think I can implement it then.
    Poncho
    @poncho-guerrero
    Screen Shot 2019-06-18 at 2.07.45 PM.png
    Hey everyone! I'm getting this weird error that adds "alias" to all my items.
    Anyone knows what causes this and how to correct it?
    Poncho
    @poncho-guerrero
    Ok, so I just noticed two things:
    1. This chat is inactive and I'm probably not getting an answer here. (I'll leave my findings in case some arrives with the same problem as myself)
    2. My problem is referenced in the issue SassDoc/sassdoc#536.
      TL;DR the solution is to run npm i sassdoc-theme-default so that the default sassdoc theme is overwritten by the latest version (2.8.2 during the time of this message).
    Casey Hunt
    @caseymhunt
    I'm looking to generate sassdocs locally based on the package.json version. Where should I get started in the sassdoc config to make that happen?
    Casey Hunt
    @caseymhunt
    The desired outcome would be something like generating sassdocs into dist/sassdoc-<VERSION> rather than the default folder.