.gitignore added
[dotfiles/.git] / .config / coc / extensions / node_modules / coc-prettier / node_modules / stylelint / lib / rules / at-rule-empty-line-before / README.md
diff --git a/.config/coc/extensions/node_modules/coc-prettier/node_modules/stylelint/lib/rules/at-rule-empty-line-before/README.md b/.config/coc/extensions/node_modules/coc-prettier/node_modules/stylelint/lib/rules/at-rule-empty-line-before/README.md
new file mode 100644 (file)
index 0000000..aadbd6c
--- /dev/null
@@ -0,0 +1,373 @@
+# at-rule-empty-line-before
+
+Require or disallow an empty line before at-rules.
+
+```css
+a {}
+          /* ← */
+@media {} /* ↑ */
+/**          ↑
+ *   This line */
+```
+
+If the at-rule is the very first node in a stylesheet then it is ignored. `@import` in Less will also be ignored.
+
+The `--fix` option on the [command line](../../../docs/user-guide/cli.md#autofixing-errors) can automatically fix all of the problems reported by this rule. We recommend to enable [`indentation`](../indentation/README.md) rule for better autofixing results with this rule.
+
+## Options
+
+`string`: `"always"|"never"`
+
+### `"always"`
+
+There *must always* be an empty line before at-rules.
+
+The following patterns are considered violations:
+
+```css
+a {} @media {}
+```
+
+```css
+a {}
+@media {}
+```
+
+The following patterns are *not* considered violations:
+
+```css
+a {}
+
+@media {}
+```
+
+### `"never"`
+
+There *must never* be an empty line before at-rules.
+
+The following patterns are considered violations:
+
+```css
+a {}
+
+@media {}
+```
+
+The following patterns are *not* considered violations:
+
+```css
+a {} @media {}
+```
+
+```css
+a {}
+@media {}
+```
+
+## Optional secondary options
+
+### `except: ["after-same-name", "inside-block", "blockless-after-same-name-blockless", "blockless-after-blockless", "first-nested"]`
+
+#### `"after-same-name"`
+
+Reverse the primary option for at-rules that follow another at-rule with the same name.
+
+This means that you can group your at-rules by name.
+
+For example, with `"always"`:
+
+The following patterns are *not* considered violations:
+
+```css
+@charset "UTF-8";
+
+@import url(x.css);
+@import url(y.css);
+
+@media (min-width: 100px) {}
+@media (min-width: 200px) {}
+```
+
+```css
+a {
+
+  @extends .foo;
+  @extends .bar;
+
+  @include x;
+  @include y {}
+}
+```
+
+#### `"inside-block"`
+
+Reverse the primary option for at-rules that are nested.
+
+For example, with `"always"`:
+
+The following patterns are considered violations:
+
+```css
+a {
+
+  @extend foo;
+  color: pink;
+}
+
+b {
+  color: pink;
+
+  @extend foo;
+}
+```
+
+The following patterns are *not* considered violations:
+
+```css
+a {
+  @extend foo;
+  color: pink;
+}
+
+b {
+  color: pink;
+  @extend foo;
+}
+```
+
+#### `"blockless-after-same-name-blockless"`
+
+Reverse the primary option for blockless at-rules that follow another blockless at-rule with the same name.
+
+This means that you can group your blockless at-rules by name.
+
+Shared-line comments do not affect this option.
+
+For example, with `"always"`:
+
+The following patterns are *not* considered violations:
+
+```css
+@charset "UTF-8";
+
+@import url(x.css);
+@import url(y.css);
+```
+
+```css
+@charset "UTF-8";
+
+@import url(x.css); /* comment */
+@import url(y.css);
+```
+
+```css
+a {
+
+  @extends .foo;
+  @extends .bar;
+
+  @include loop;
+  @include doo;
+}
+```
+
+#### `"blockless-after-blockless"`
+
+Reverse the primary option for at-rules within a blockless group.
+
+Shared-line comments do not affect this option.
+
+For example, with `"always"`:
+
+The following patterns are considered violations:
+
+```css
+@import url(x.css);
+
+@import url(y.css);
+
+@media print {}
+```
+
+The following patterns are *not* considered violations:
+
+```css
+@import url(x.css);
+@import url(y.css);
+
+@media print {}
+```
+
+```css
+@import url(x.css); /* comment */
+@import url(y.css);
+
+@media print {}
+```
+
+#### `"first-nested"`
+
+Reverse the primary option for at-rules that are nested and the first child of their parent node.
+
+For example, with `"always"`:
+
+The following patterns are considered violations:
+
+```css
+a {
+
+  @extend foo;
+  color: pink;
+}
+
+b {
+  color: pink;
+  @extend foo;
+}
+```
+
+The following patterns are *not* considered violations:
+
+```css
+a {
+  @extend foo;
+  color: pink;
+}
+
+b {
+  color: pink;
+
+  @extend foo;
+}
+```
+
+### `ignore: ["after-comment", "inside-block", "blockless-after-same-name-blockless", "blockless-after-blockless"]`
+
+#### `"after-comment"`
+
+Ignore at-rules that come after a comment.
+
+Shared-line comments do not trigger this option.
+
+The following patterns are *not* considered violations:
+
+```css
+/* comment */
+@media {}
+```
+
+```css
+/* comment */
+
+@media {}
+```
+
+```css
+@media {} /* comment */
+
+@media {}
+```
+
+#### `"inside-block"`
+
+Ignore at-rules that are inside a declaration block.
+
+For example, with `"always"`:
+
+The following patterns are *not* considered violations:
+
+```css
+a {
+  @extend foo;
+  color: pink;
+}
+
+a {
+
+  @extend foo;
+  color: pink;
+}
+
+b {
+  color: pink;
+  @extend foo;
+}
+
+b {
+  color: pink;
+
+  @extend foo;
+}
+```
+
+#### `"blockless-after-same-name-blockless"`
+
+Ignore blockless at-rules that follow another blockless at-rule with the same name.
+
+This means that you can group your blockless at-rules by name.
+
+For example, with `"always"`:
+
+The following patterns are *not* considered violations:
+
+```css
+
+@charset "UTF-8";
+
+@import url(x.css);
+@import url(y.css);
+```
+
+```css
+a {
+
+  @extends .foo;
+  @extends .bar;
+
+  @include loop;
+  @include doo;
+}
+```
+
+#### `"blockless-after-blockless"`
+
+Ignore blockless at-rules that follow another blockless at-rule.
+
+For example, with `"always"`:
+
+The following patterns are *not* considered violations:
+
+```css
+@import url(x.css);
+
+@import url(y.css);
+
+@media print {}
+```
+
+```css
+@import url(x.css);
+@import url(y.css);
+
+@media print {}
+```
+
+### `ignoreAtRules: ["array", "of", "at-rules"]`
+
+Ignore specified at-rules.
+
+For example, with `"always"`.
+
+Given:
+
+```js
+["import"]
+```
+
+The following patterns are *not* considered violations:
+
+```css
+@charset "UTF-8";
+@import {}
+```