Setting variable to a font stack can throw false namingConvention warning

[simenb]

Setting variable to a font stack can throw false namingConvention warning

[awayken]

This might be related. In the following file, I get the same namingConvention issue but I'm setting a tuple instead of a font stack. Rather than make another issue, I'm including it here. Let me know if you'd like this broken out.

fontfaces.styl

$font-faces = (Regular 400) (Medium 500)

for $face in $font-faces {
    @font-face {
        font-family: $face[ 1 ];
        font-weight: $face[ 2 ];
    }
}

Output:

Warning:  preferred naming convention is lowercase-dash
File: ../temp-stylus/fontfaces.styl
Line: 1: $font-faces = (Regular 400) (Medium 500)

[rossPatton]

not fully sure how to tackle this one without knowing the context of where a variable is used, and that would require a lot of changes to stylint. var/class/id names can be anything, and font names can be anything.

just use the @stylint off toggle? in my experience, seeing up your font stack is usually just done once, in one place and then used everywhere

[awayken]

The project I've been running Stylint against only has two places where I've run into this issue, so I'm willing to use the toggle technique. If I start to run into this more frequently, I might reopen this comment to further the discussion.

Thanks for looking into it!