Switch to enforcing single quotes

[jaydenseric]

Single quotes are a better for three main reasons:

1. Consistency with the most popular PHP and JS style guides (see eslint-config-standard).
2. Easier to type (no shift key press). This allows faster typing and reduces the risk of RSI.
3. Visually less noise. Single quotes are a simpler symbol and are cleaner to look at.

Rules to tweak:

• font-family-name-quotes
• function-url-quotes
• string-quotes

[jaydenseric]

I would seriously consider enforcing no quotes, as it is perfectly valid not to use them and less is more. The only downside is syntax highlighters are often not that smart and usually highlight the strings differently without quotes. I see that as an issue with the highlighters not following W3C specs properly though. It seems stylelint documentation examples do not use quotes, see at-rule-empty-line-before.

[jeddy3]

@jaydenseric Thanks for the input. You raise some good points.

@davidtheclark I went back through the style guides linked to from the README and found quotes to be more divisive than I originally thought. There isn't any consistency across the style guides. Perhaps we should follow eslint's lead and not specify a quotes config.

[davidtheclark]

I agree that there's no consistent standard, so let's cut it out,

On Mar 15, 2016, at 1:41 AM, Richard Hallows notifications@github.com wrote:

@jaydenseric Thanks for the input. You raise some good points.

I would seriously consider enforcing no quotes

@davidtheclark I went back through the style guides linked to from the README and found quotes to be more divisive than I originally thought. There isn't any consistency across the style guides. Perhaps we should follow eslint's lead and not specify a quotes config.

—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
#14 (comment)

[oliverturner]

Additionally, I'm finding that the following

  "stylelint": {
    "extends": "stylelint-config-standard",
    "rules": {
      "string-quotes": "single"
    }
  }

creates a Kafkaesque paradox wherein I can only be wrong:

  font-family: 'Helvetica Neue', Helvetica, Arial, sans-serif;

=> Expected double quotes around font-family name "Helvetica Neue" (font-family-name-quotes)

  font-family: "Helvetica Neue", Helvetica, Arial, sans-serif;

=> Expected single quotes (string-quotes)

[jeddy3]

@oliverturner This is because each rule is standalone and sometimes it's possible to configure rules so that they conflict with one another. In this instance you're only overriding the string-quotes rule to "single", but font-family-name-quotes is still set to "double-where-recommended" within the config. So, you'll need to override both rules to avoid this paradox.

Going forward, we're going to remove the quote rules and so it'll be less likely someone will run into the issue you've had.

[santanajames]

Seems like double quotes were added back for string-quotes in version 23.0.0. Curious about the reasoning behind this given the decision mentioned by @jeddy3.

[jeddy3]

@santanajames See #198 (comment).

The emphasis of the config changed:

• from being foundational based on the commonality found in userland style guides
• to being something complete that helps users author CSS that looks like the examples in the specs (which nearly always use double quotes as far as I can tell)

The conflicts mentioned above were resolved a couple of years ago. The options for rules like font-family-name-quotes were changed to be agnostic of the type of quote.

I would seriously consider enforcing no quotes, as it is perfectly valid not to use them and less is more

Unquoted url functions are now legacy.