1
0
mirror of https://github.com/thangisme/notes.git synced 2024-11-01 10:37:25 -04:00
notes/node_modules/stylelint/lib/rules/declaration-block-properties-order/README.md

557 lines
8.4 KiB
Markdown
Raw Normal View History

2017-03-09 13:16:08 -05:00
# declaration-block-properties-order
***Deprecated: instead use the community [`stylelint-order`](https://github.com/hudochenkov/stylelint-order) plugin pack.***
Specify the order of properties within declaration blocks.
```css
a {
color: pink;
top: 0;
}
/** ↑
* These properties */
```
Prefixed properties *must always* be alphabetically ordered and *must always* precede the unprefixed version.
This rule ignores variables (`$sass`, `@less`, `--custom-property`).
## Options
`string|array`: `"alphabetical"|["array", "of", "unprefixed", "property", "names", "or", "group", "objects"]`
### `"alphabetical"`
Properties *must always* be ordered alphabetically.
The following patterns are considered warnings:
```css
a {
top: 0;
color: pink;
}
```
```css
a {
-moz-transform: scale(1);
transform: scale(1);
-webkit-transform: scale(1);
}
```
The following patterns are *not* considered warnings:
```css
a {
color: pink;
top: 0;
}
```
```css
a {
-moz-transform: scale(1);
-webkit-transform: scale(1);
transform: scale(1);
}
```
### `["array", "of", "unprefixed", "property", "names", "or", "group", "objects"]`
Within an order array, you can include
- unprefixed property names
- group objects with these properties:
- `order ("strict"|"flexible")`: If `"strict"` (the default), the properties in this group must come in the order specified. If `"flexible"`, the properties can be in any order as long as they are grouped correctly.
- `properties (array of strings)`: The properties in this group.
There are some important details to keep in mind:
**By default, unlisted properties will be ignored.** So if you specify an array and do not include `display`, that means that the `display` property can be included before or after any other property. *This can be changed with the `unspecified` option* (see below).
**If an (unprefixed) property name is not included in your array and it contains a hyphen (e.g. `padding-left`), this rule will look for the string before that first hyphen in your array (e.g. `padding`) and use that position.** This means that you do not have to specify each extension of the root property; you can just specify the root property and the extensions will be accounted for.
For example, if you have included `border` in your array but not `border-top`, the rule will expect `border-top` to appear in the same relative position as `border`.
Other relevant rules include `margin`, `border`, `animation`, `transition`, etc.
Using this fallback, the order of these hyphenated relative to their peer extensions (e.g. `border-top` to `border-bottom`) will be *arbitrary*. If you would like to enforce a specific ordering (e.g. always put `border-right` before `border-left`), you should specify those particular names in your array.
Given:
```js
["transform", "top", "color"]
```
The following patterns are considered warnings:
```css
a {
color: pink;
top: 0;
}
```
```css
a {
-moz-transform: scale(1);
transform: scale(1);
-webkit-transform: scale(1);
}
```
The following patterns are *not* considered warnings:
```css
a {
top: 0;
color: pink;
}
```
```css
a {
-moz-transform: scale(1);
-webkit-transform: scale(1);
transform: scale(1);
}
```
Given:
```js
["padding", "color"]
```
The following patterns are considered warnings:
```css
a {
color: pink;
padding: 1em;
}
```
```css
a {
color: pink;
padding-top: 1em;
}
```
```css
a {
padding-left: 2em;
color: pink;
padding-top: 1em;
}
```
The following patterns are *not* considered warnings:
```css
a {
padding: 1em;
color: pink;
}
```
```css
a {
padding-top: 1em;
color: pink;
}
```
```css
a {
padding-left: 2em;
padding-top: 1em;
color: pink;
}
```
```css
a {
padding-top: 1em;
padding-left: 2em;
color: pink;
}
```
Given:
```js
["my", "font-smoothing", "color"]
```
Where `font-smoothing` is the unprefixed version of proprietary browser property `-webkit-font-smoothing` and `my` is a user-defined shorthand property.
The following patterns are considered warnings:
```css
a {
color: pink;
-webkit-font-smoothing: antialiased;
}
```
```css
a {
-webkit-font-smoothing: antialiased;
my-property: 2em;
}
```
```css
a {
my-property: 2em;
color: pink;
my-other-property: 1em;
}
```
The following patterns are *not* considered warnings:
```css
a {
-webkit-font-smoothing: antialiased;
color: pink;
}
```
```css
a {
my-property: 2em;
-webkit-font-smoothing: antialiased;
}
```
```css
a {
my-property: 2em;
my-other-property: 1em;
color: pink;
}
```
```css
a {
my-other-property: 1em;
my-property: 2em;
color: pink;
}
```
Given:
```js
["padding", "padding-top", "padding-right", "padding-bottom", "padding-left", "color"]
```
The following patterns are considered warnings:
```css
a {
padding-left: 2em;
padding-top: 1em;
padding: 1em;
color: pink;
}
```
The following patterns are *not* considered warnings:
```css
a {
padding-top: 1em;
padding-right: 1em;
padding-bottom: 0.5em;
padding-left: 0.5em;
color: pink;
}
```
```css
a {
padding: 1em;
padding-right: 2em;
padding-left: 2.5em;
color: pink;
}
```
Given:
```js
[
{
properties: [
"height",
"width",
],
},
{
properties: [
"font-size",
"font-weight",
],
},
]
```
The following patterns are considered warnings:
```css
a {
width: 2px;
height: 1px;
font-size: 2px;
font-weight: bold;
}
```
```css
a {
width: 2px;
height: 1px;
font-size: 2px;
font-weight: bold;
}
```
The following patterns are *not* considered warnings:
```css
a {
height: 1px;
width: 2px;
font-size: 2px;
font-weight: bold;
}
```
```css
a {
height: 1px;
width: 2px;
font-size: 2px;
font-weight: bold;
}
```
Given:
```js
[
"height",
"width",
{
order: "flexible",
properties: [
"color",
"font-size",
"font-weight",
],
},
]
```
The following patterns are considered warnings:
```css
a {
height: 1px;
font-weight: bold;
width: 2px;
}
```
```css
a {
width: 2px;
height: 1px;
font-weight: bold;
}
```
```css
a {
height: 1px;
color: pink;
width: 2px;
font-weight: bold;
}
```
The following patterns are *not* considered warnings:
```css
a {
height: 1px;
width: 2px;
color: pink;
font-size: 2px;
font-weight: bold;
}
```
```css
a {
height: 1px;
width: 2px;
font-size: 2px;
color: pink;
font-weight: bold;
}
```
## Optional secondary options
### `unspecified: "top"|"bottom"|"bottomAlphabetical"|"ignore"`
These options only apply if you've defined your own array of properties.
Default behavior is the same as `"ignore"`: an unspecified property can appear before or after any other property.
With `"top"`, unspecified properties are expected *before* any specified properties. With `"bottom"`, unspecified properties are expected *after* any specified properties. With `"bottomAlphabetical"`, unspecified properties are expected *after* any specified properties, and the unspecified properties are expected to be in alphabetical order.
Given:
```js
[["color", "background"], { unspecified: "ignore" }]
```
The following patterns are *not* considered warnings:
```css
a {
color: pink;
background: orange;
left: 0;
}
```
```css
a {
left: 0;
color: pink;
background: orange;
}
```
```css
a {
color: pink;
left: 0;
background: orange;
}
```
Given:
```js
[["color", "background"], { unspecified: "top" }]
```
The following patterns are considered warnings:
```css
a {
color: pink;
background: orange;
left: 0;
}
```
```css
a {
color: pink;
left: 0;
background: orange;
}
```
The following patterns are *not* considered warnings:
```css
a {
left: 0;
color: pink;
background: orange;
}
```
Given:
```js
[["color", "background"], { unspecified: "bottom" }]
```
The following patterns are considered warnings:
```css
a {
left: 0;
color: pink;
background: orange;
}
```
```css
a {
color: pink;
left: 0;
background: orange;
}
```
The following patterns are *not* considered warnings:
```css
a {
color: pink;
background: orange;
left: 0;
}
```
Given:
```js
[["composes"], { unspecified: "bottomAlphabetical" }]
```
The following patterns are considered warnings:
```css
a {
align-items: flex-end;
composes: b;
left: 0;
}
```
```css
a {
composes: b;
left: 0;
align-items: flex-end;
}
```
The following patterns are *not* considered warnings:
```css
a {
composes: b;
align-items: flex-end;
left: 0;
}
```